Date: Tue, 23 Jun 1998 11:04:22 -0400 (EDT) From: ADRIAN Filipi-Martin <adrian@ubergeeks.com> To: Keith Woodworth <kwoody@citytel.net> Cc: Bryce Newall <data@dreamhaven.net>, freebsd-questions@FreeBSD.ORG Subject: Re: Oops, killed init Message-ID: <Pine.BSF.3.96.980623110120.1782B-100000@lorax.ubergeeks.com> In-Reply-To: <Pine.BSF.3.91.980622232436.16435A-100000@mybsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 22 Jun 1998, Keith Woodworth wrote: > > > On Mon, 22 Jun 1998, Bryce Newall wrote: > > > > a big deal but I wont know what happedned to the machine till I get home > > > in about 5 hours but want some idea on what state the machine might be in > > > > It will be in a state of confusion. :) Seriously, though, killing init > > basically brings your machine to a halt, since init is the master process. > > You'll probably have to hard-reset your machine when you get home, since > > init itself is what processes ctrl-alt-del, and since init isn't > > running... > > A follow-up here...got home and the console said enter path to sh or hit > return for sh: You simply brought it down to single user mode. This is all documented in the init(8) manpage. In fact you cannot "kill" init. Try "kill -KILL 1" and see what happens. Nothing. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980623110120.1782B-100000>