[ From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX"  7-AUG-1990 08:59:05.02  To:	MRGATE::"ARISIA::EVERHART" CC:	& Subj:	Re: Logging into OPA0: Remotely?  * Received:  by crdgw1.ge.com (5.57/GE 1.70)( 	 id AA01958; Mon, 6 Aug 90 23:47:06 EDT/ Message-Id:  <9008070347.AA01958@crdgw1.ge.com> Z Received: From SOL1.GPS.CALTECH.EDU by CRVAX.SRI.COM with TCP; Mon,  6 AUG 90 15:17:35 PDT Date: 6 Aug 1990 14:14:18 EST ( From: Carl.J.Lydick@SOL1.GPS.CALTECH.EDU To: info-vax@sri.com) Subject: Re: Logging into OPA0: Remotely? * X-Vms-Original-To: INET%"info-vax@sri.com"    L  > I have just had a problem this weekend.  I needed to reboot a MicroVax IIN  > that I couldn't have physical access to.  I already know that RT: terminalsI  > can issue the reboot commands but for this, I had to use Xerox Network C  > terminal drivers which get killed too early, hanging the system.   L  > Q:  I remember seeing a script whereby one can in effect seize a terminalL  > and input keystrokes onto it.  I believe that it is also possible to read/  > the text that is displayed on that terminal.   
  > Any Ideas?   6 Run the following procedure from a privileged account:+ 	$ COPY SYS$INPUT: SYS$MANAGER:SHUTDOWN.TMP  	$ DECK # 	$ DELETE SYS$MANAGER:SHUTDOWN.TMP;  	$ SET NOVERIFY F 	$ @SYS$SYSTEM:SHUTDOWN 0 1 0 1 0 1 NONE !Use your own parameters here 	$EOD B 	$ RUN/DETACHED/INPUT=SYS$MANAGER:SHUTDOWN.TMP SYS$SYSTEM:LOGINOUTO This will run the shutdown procedure as a detached process, and will get around  the problem you describe.   