From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JhS1F-0003kL-GT for garchives@archives.gentoo.org; Thu, 03 Apr 2008 16:10:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D2EA4E04D9; Thu, 3 Apr 2008 16:10:27 +0000 (UTC) Received: from exchange.gridapp.com (exchange.gridapp.com [160.79.39.130]) by pigeon.gentoo.org (Postfix) with ESMTP id A6D4BE04D9 for ; Thu, 3 Apr 2008 16:10:27 +0000 (UTC) Received: from [10.100.3.141] ([10.100.3.141]) by exchange.gridapp.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 3 Apr 2008 12:10:27 -0400 Message-ID: <47F50172.8070904@wrkhors.com> Date: Thu, 03 Apr 2008 12:10:26 -0400 From: Steven Lembark User-Agent: Thunderbird 2.0.0.12 (X11/20080303) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Emergency shutdown, how to? References: <47EC9F50.5070503@bellsouth.net> <68b1e2610804020636rba3f3afw32bad1494c62cc24@mail.gmail.com> <47F3AB3D.3020202@wrkhors.com> <200804021928.01885.volker.armin.hemmann@tu-clausthal.de> <47F3DC48.3010906@bellsouth.net> In-Reply-To: <47F3DC48.3010906@bellsouth.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 03 Apr 2008 16:10:27.0120 (UTC) FILETIME=[3AF2EB00:01C895A5] X-Archives-Salt: 5a0b96a3-6115-4384-92b3-47f1ccb3a4b7 X-Archives-Hash: 8f9e38ed337431962a114f6f59546711 > Basically, this is not intended to be used to shutdown a puter on a > regular basis, unless you burn out P/S's on a daily basis. O-o > > Just didn't want someone to be using this on a regular basis and then > wondering why their system has a new nickname, FUBAR. :'( In most cases you'll find that 'shutdown -h now' takes only a few seconds. If you're typing againsed the clock and don't to it every day then the SysReq tecnhique is somewhat error prone. In most cases the stuff that can't handle a crash tends to live at higher runlevels anyway and gets stopped when you exit rl 3; stuff that gets started at boot time are more likely service daemons that can easily handle a reset. Even if your shutdown croaks halfway through the stuff, chances are that got shut down first was the most fragile anyway (e.g., databases that had to flush cache) and you got whatever you could cleaned up however fast you could do it and you live with the rest on restart. -- Steven Lembark +1 888 359 3508 Workhorse Computing 85-09 90th St lembark@wrkhors.com Woodhaven, NY 11421 -- gentoo-user@lists.gentoo.org mailing list