Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!uflorida!haven!cvl!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: System V / SIGCLD questions...
Message-ID: <17492@mimsy.UUCP>
Date: 13 May 89 13:40:17 GMT
References: <565@lehi3b15.csee.Lehigh.EDU> <17457@mimsy.UUCP> <567@lehi3b15.csee.Lehigh.EDU>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 10

In article <567@lehi3b15.csee.Lehigh.EDU> murrey@lehi3b15.csee.Lehigh.EDU
(Erik Murrey) writes:
>So my solution is to reset the sigcld signal after the wait(). Doesn't
>this leave a window where a child can die, and I won't ever know about
>it?

No.  Reread <17457@mimsy.UUCP>.  Any `lost' SIGCLD is `regenerated'.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris