<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>I wonder if you could set the console port to listen on a named pipe, and then use expect to connect and execute scripts?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>That way you can use one to setup the boot environment from PROM (if needed) boot, then once it’s booted, you can ‘login’ and then execute scripts to check system/network status, then another to shut it down?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’ve been driving TME on Windows 10 using the Linux subsystem with a named pipe to talk to it, and it seems okay enough, as I really have no other way to interact with the ‘serial’ console, and doing this allows me to nohup it, and talk to it as I want to.. Especially as the NIC that TME emulates isn’t supported by SunOS 2.0</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:lars@nocrew.org">Lars Brinkhoff</a><br><b>Sent: </b>Friday, November 29, 2019 1:39 PM<br><b>To: </b><a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br><b>Subject: </b>Re: [Simh] Unattended background SIMH process</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Seth J. Morabito wrote:</p><p class=MsoNormal>> Has anyone got a clean solution for running a background SIMH process</p><p class=MsoNormal>> that doesn't involve `screen` or `tmux`?</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have also been in search of a solution for this. I'm OK with using</p><p class=MsoNormal>screen if necessary.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> I would like to create an init script or systemd module that will kick</p><p class=MsoNormal>> off a simulator as a daemon process that can start up on host boot, and</p><p class=MsoNormal>> shut down on host shutdown.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>It's the shutting down part that's the problem for me. The operating</p><p class=MsoNormal>systems I'm interested need to have a user login and type a command to</p><p class=MsoNormal>shut down cleanly. This is hard to do reliably.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Possible workarounds for this include abusing the hardware power fail</p><p class=MsoNormal>interrupt to initiate shutdown, or listening for a signal from the</p><p class=MsoNormal>network.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>Simh mailing list</p><p class=MsoNormal>Simh@trailing-edge.com</p><p class=MsoNormal>http://mailman.trailing-edge.com/mailman/listinfo/simh</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>