Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!mit-eddie!bacchus!husc6!ut-sally!ut-ngp!dlnash
From: dlnash@ut-ngp.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: help for routine to handle exit conditions
Message-ID: <4735@ut-ngp.UUCP>
Date: Fri, 20-Feb-87 11:17:12 EST
Article-I.D.: ut-ngp.4735
Posted: Fri Feb 20 11:17:12 1987
Date-Received: Sat, 21-Feb-87 06:30:23 EST
References: <972@unc.unc.UUCP> <1006@cartan.Berkeley.EDU>
Distribution: na
Organization: UTexas Computation Center, Austin, Texas
Lines: 16

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).

				Don Nash

UUCP:    ...!{ihnp4, allegra, seismo!ut-sally}!ut-ngp!dlnash
ARPA:    dlnash@ngp.CC.UTEXAS.EDU
BITNET:	 CCEU001@UTADNX, DLNASH@UTADNX