Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!cartan!brahms.Berkeley.EDU!ballou
From: ballou@brahms.Berkeley.EDU.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: help for routine to handle exit conditions
Message-ID: <1015@cartan.Berkeley.EDU>
Date: Fri, 20-Feb-87 22:12:15 EST
Article-I.D.: cartan.1015
Posted: Fri Feb 20 22:12:15 1987
Date-Received: Sat, 21-Feb-87 16:36:58 EST
References: <972@unc.unc.UUCP> <1006@cartan.Berkeley.EDU> <4735@ut-ngp.UUCP>
Sender: daemon@cartan.Berkeley.EDU
Reply-To: ballou@brahms.Berkeley.EDU (Kenneth R. Ballou)
Distribution: na
Organization: Math Dept. UC Berkeley
Lines: 24

In article <4735@ut-ngp.UUCP> dlnash@ut-ngp.UUCP (Donald L. Nash) writes:
>In article <1006@cartan.Berkeley.EDU>, ballou@brahms.Berkeley.EDU (Kenneth R. Ballou) writes:
>> 
>> 	This can lead to interesting race conditions; it is possible for
>> your process to be sent the same signal twice before it has had a chance
>> to reset the signal handler for that particular signal.
>>
>
>This does not happen because when a signal is delivered, it is blocked from
>further occurrence, much like an interrupt.  This is from the 4.2 BSD man
>page for sigvec(2).

	Careful!  It is true that this is the case for BSD, but I will point
out that (to the best of my knowledge) it is BSD specific behavior.  I seem
to recall a discussion some time back about SIGCHILD in comp.unix.questions
(or comp.unix.wizards) where this was pointed out.  Or maybe my mind has
completely checked out ...


--------
Kenneth R. Ballou			ARPA:  ballou@brahms.berkeley.edu
Department of Mathematics		UUCP:  ...!ucbvax!brahms!ballou
University of California
Berkeley, California  94720