Date: Tue, 29 Sep 2009 13:08:58 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: FreeBSD Current <freebsd-current@freebsd.org>, d@delphij.net Subject: Re: [PATCH] Shutdown cooloff feature Message-ID: <86fxa6gg8l.fsf@ds4.des.no> In-Reply-To: <E1MsXso-0005Eg-CY@kabab.cs.huji.ac.il> (Daniel Braniss's message of "Tue, 29 Sep 2009 10:16:26 %2B0200") References: <4AC141B0.4090705@delphij.net> <E1MsXso-0005Eg-CY@kabab.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
Daniel Braniss <danny@cs.huji.ac.il> writes: > Xin LI <delphij@delphij.net> writes: > > I'm not sure if anyone would find this useful: > >=20 > > - If a shutdown is initiated from a tty -and- > > - It's not a restart -and- > > - The time parameter is set to "now" > >=20 > > Then, the shutdown(8) program would give something like this: > >=20 > > Shutting down <hostname> NOW, press ^C within 5 seconds to cancel... > >=20 > > So the user would get a chance to terminate it before it's too late. > I know we are living in a virtual world, where even shutting down > a computer is just a 'wish', but lets keep some sanity, now means now. The "now" is not an issue; I think his point is that you *really* don't want to accidentally type "shutdown -h now" or "shutdown now" instead of "shutdown -r now" in an ssh session to a remote system - especially at 6 pm on a Friday night when the machine is in a colo center that's only manned during business hours. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86fxa6gg8l.fsf>