Date: Mon, 7 Feb 2011 19:26:17 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Devin Teske <dteske@vicor.com> Cc: Eitan Adler <lists@eitanadler.com>, Alokat <mailing@alokat.org>, freebsd-questions@freebsd.org Subject: Re: shutdown computer after the halt command Message-ID: <AANLkTimXnCVBbZ1xz=jRMXGfg6Bka2vns_icg%2B06O9ZT@mail.gmail.com> In-Reply-To: <1297127587.2564.8.camel@dt.vicor.com> References: <4D508917.3000202@alokat.org> <1297124530.2564.5.camel@dt.vicor.com> <AANLkTi=Wd-z_xphXJKUfrba8wmFRoE9Kf%2BqYcDuvDSjh@mail.gmail.com> <1297127587.2564.8.camel@dt.vicor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 7, 2011 at 7:13 PM, Devin Teske <dteske@vicor.com> wrote: > There's no technical reason to avoid using halt directly other than the > fact that shutdown sends a message to connected users while halt does > not. > -- > Devin > > P.S. I welcome the rebuttle as a learning experience if the above is not > 100% accurate and true (but be-warned... I went around the office > polling _really_ old UNIX hands before making the above statement). > I used to believe that until I was shown I was wrong. The easiest way to see you're wrong is to drop to ttyv0 then do one of each like a reboot then a shutdown -r now. In the latter case, you'll notice /etc/rc.d/ and /usr/local/etc/rc.d/ stop scripts being processed but not so in the former. In both types of shutdowns, everything *should* exit cleanly but processes are terminated with different signals and certain types of applications really need the full rc stop script to end cleanly like HAST and CARP for example. shutdown -r/p is a really good habit to form. FWIW, someone also stated reboot on Linux behaves like shutdown -r now so that I sure contributes to the confusion. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimXnCVBbZ1xz=jRMXGfg6Bka2vns_icg%2B06O9ZT>