Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!gem.mps.ohio-state.edu!pacific.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ucsfcgl!cca.ucsf.edu!wet!epsilon
From: epsilon@wet.UUCP (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: NeXTs on & off
Message-ID: <656@wet.UUCP>
Date: 10 Oct 89 18:12:13 GMT
References: <1923@cunixc.cc.columbia.edu> <630@wet.UUCP> <1932@cunixc.cc.columbia.edu>
Reply-To: epsilon@wet.UUCP (Eric P. Scott)
Organization: Wetware Diversions, San Francisco
Lines: 13

In article <1932@cunixc.cc.columbia.edu> brad@woof.columbia.edu
	(Brad Garton) writes:
>Right after I set mine up we had a small power glitch (Hugo was passing
>through Pennsylvania, we felt a minor bit of it here in NJ).  My machine
>got kicked into the monitor, had to reboot it "by hand".  No problem
>coming back up after the "b" command was entered, though.

Ah, but this is manual intervention.  When disaster strikes your
critical server, odds are no one's going to be around.  It's got
to be settable to come up all the way on its own when power's
restored... or I want a NeXT with "remote console" capability!

					-=EPS=-