Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site ccvaxa.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!ihnp4!inuxc!pur-ee!uiucdcs!ccvaxa!preece
From: preece@ccvaxa.UUCP
Newsgroups: net.unix-wizards
Subject: Re: system will not shutdown
Message-ID: <47500011@ccvaxa.UUCP>
Date: Sun, 3-Mar-85 00:42:00 EST
Article-I.D.: ccvaxa.47500011
Posted: Sun Mar  3 00:42:00 1985
Date-Received: Wed, 20-Feb-85 03:21:34 EST
References: <93600004@siemens.UUCP>
Lines: 23
Nf-ID: #R:siemens:93600004:ccvaxa:47500011:000:841
Nf-From: ccvaxa!preece    Feb 17 23:42:00 1985


>	We seem to be having a problem with /etc/shutdown.  To shut
>	the system down, I usually use the command:
>
>	/etc/shutdown -h +5 "comment"
>
>	Shutdown starts, gives back its pid number, then just hangs there
>	forever.
----------
This could be due to 4.2 signals.  Shutdown uses alarm signals to
break out of its attempts to write messages out to user terminals.
In 4.2 those signal routines don't do what they need to do; after
leaving the signal handler the interrupted routine is restarted,
leaving you blocked again.

The fix is to do a setjmp before the potentially blocking code and
then do a longjmp in the alarm handling routine.  I would attach diffs,
but our shutdown has been hacked for other things, too, and it would
be too much work to isolate those few lines.

scott preece
gould/csd - urbana
ihnp4!uiucdcs!ccvaxa!preece