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 1JhpSd-0002cw-3o for garchives@archives.gentoo.org; Fri, 04 Apr 2008 17:12:19 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 30B6BE08A4; Fri, 4 Apr 2008 17:12:17 +0000 (UTC) Received: from duke.localdomain (p78-102.acedsl.com [66.114.78.102]) by pigeon.gentoo.org (Postfix) with ESMTP id E9040E08A4 for ; Fri, 4 Apr 2008 17:12:16 +0000 (UTC) Received: from [127.0.0.1] (duke.wrkhors.com [127.0.0.1]) by duke.localdomain (Postfix) with ESMTP id 34BA728D6A5 for ; Fri, 4 Apr 2008 13:04:01 -0400 (EDT) Message-ID: <47F65F81.8040701@wrkhors.com> Date: Fri, 04 Apr 2008 13:04:01 -0400 From: Steven Lembark Organization: Workhorse Computing User-Agent: Thunderbird 2.0.0.9 (X11/20071212) 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> <47F50172.8070904@wrkhors.com> <47F51ED5.1030608@bellsouth.net> <47F5322F.5080701@wrkhors.com> <47F57A1C.7060905@bellsouth.net> In-Reply-To: <47F57A1C.7060905@bellsouth.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: db6ef140-cb7e-4a0a-a65b-52e82846bcb8 X-Archives-Hash: 4ad68617dabdd99318b7d4f0385af242 Dale wrote: > Steven Lembark wrote: >> >> > Well, this one takes longer. Just the foldingathome takes about 20 >> > seconds or more to shutdown. It can take over 60 seconds at times. >> > That service for some reason has to completely shutdown before the >> > others start to shutdown. The others will shutdown in parallel like I >> > have set up. Then there is all the other services that have to stop. >> > Quite literally, I only had seconds to shutdown since the P/S was >> > stinking like a skunk. I just needed to umnount the file systems and >> > power off as fast as possible. I didn't want to just pull the plug but >> > I needed a shutdown that fast. >> >> Hackint the shutdowns to background the shutdown >> op and return is usually pretty simple -- don't know >> why more app's don't do that by default. >> >> 'halt' will get you down with little typing if you >> want to bypass the init scripts; so will "kill -TERM 1". >> Add a 'sync' before either of them and you'll probably >> be able to come up with minimal trouble. >> > > What's the difference between halt command and shutdown? I thought they > were basically the same thing. > > Also, in case you missed it. I have a service, foldingathome, that > takes a while to stop and no other service can be stopped in parallel > with this one. That is one of my key sticking points with the > shutdown. Most of the others are pretty fast. I just needed the > quickest *clean* shutdown I could get. > Thanks I have four FAH jobs running on my compute server. I can "kill -TERM fah6" in about 0.70 sec here, they start up again and just keep going. FAH is pretty robust when it comes to restarts; again if you crash the proc's then it won't be any worse than the outcome of loosing power: FAH will have to pick up its pieces and keep going. At least with "halt -f" you'll get the kernel space cleaned up. Halt will stop the O/S (see note from manpage, below). In this case a 'halt -f' would get the system down about as quickly as possible without just hitting the reset button. NOTES Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when /var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to do a hard halt or reboot. -- Steven Lembark 85-09 90th St. Workhorse Computing Woodhaven, NY, 11421 lembark@wrkhors.com +1 888 359 3508 -- gentoo-user@lists.gentoo.org mailing list