Date: Fri, 10 Dec 2010 00:46:57 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Kevin Oberman <oberman@es.net> Cc: freebsd-stable@freebsd.org Subject: Re: /sbin/reboot Message-ID: <AANLkTikgGSyRLnDS6Oihw2u3SYjeZRrQWdSa9Z4t7UAE@mail.gmail.com> In-Reply-To: <20101210060335.BCDCC1CC12@ptavv.es.net> References: <AANLkTimEvQ7amDeFE9eG%2BO9G664jXAWb9hhSt0bU%2B3DR@mail.gmail.com> <20101210060335.BCDCC1CC12@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 10, 2010 at 12:03 AM, Kevin Oberman <oberman@es.net> wrote: > Unlike reboot, shutdown attempts to cleanly stop all processes. Things > like databases can be badly damaged by a reboot. Other processes save > state when stopped and that is lost with a reboot. > For the correct order, "shutdown -r" calls reboot which calls init which calls rc.shutdown. Doing a shutdown -r is the same as a reboot without the warning to logged in users and shutdown handles the logging instead of reboot. > Also, halt/reboot have options like -n and -q which can disrupt things worse than an unintended clean reboot. shutdown also give operator more possibilities than a clean shutdown some which could be very bad. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikgGSyRLnDS6Oihw2u3SYjeZRrQWdSa9Z4t7UAE>