From owner-freebsd-questions Fri May 5 17:29:24 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA18167 for questions-outgoing; Fri, 5 May 1995 17:29:24 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA18158 for ; Fri, 5 May 1995 17:29:16 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id SAA20302; Fri, 5 May 1995 18:33:26 -0600 Date: Fri, 5 May 1995 18:33:26 -0600 From: Nate Williams Message-Id: <199505060033.SAA20302@trout.sri.MT.net> To: kelly@fsl.noaa.gov (Sean Kelly) Cc: nate@trout.sri.MT.net, markh@stack.urc.tue.nl, questions@FreeBSD.org Subject: Re: turning off ctrlaltdel In-Reply-To: <9505052351.AA27545@yarmouth.fsl.noaa.gov> References: <199505052351.RAA20230@trout.sri.MT.net> <9505052351.AA27545@yarmouth.fsl.noaa.gov> Sender: questions-owner@FreeBSD.org Precedence: bulk [ CTL-ALT_DEL reboot ] > Nate> If you *really* want to make sure nothing happens, modify > Nate> init to ignore the signal and no matter what it will get > Nate> ignored. > > What about those times when a system's thoroughly hosed---filesystem's > unresponsive, all but a few windows hung, rlogins not working, no room > in process table, and you'd like to exec three syncs and hope for the > best, but all you can do is exec a signal off to pid 1? If you can't do a sync, chances are you can't signal pid 1. Besides, init does the same thing as you are attempting to do by killing processes and syncing the disks anyway. Nate