Xref: utzoo comp.os.os2.misc:747 comp.os.os2.apps:96 comp.os.os2.programmer:474
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!samsung!olivea!oliveb!amdahl!rtech!ingres!seg
From: seg@ingres.com (scott e garfinkle)
Newsgroups: comp.os.os2.misc,comp.os.os2.apps,comp.os.os2.programmer
Subject: Re: knowing when a child process has died
Message-ID: <1991Feb22.221517.28813@ingres.Ingres.COM>
Date: 22 Feb 91 22:15:17 GMT
References: <15458@uswat.UUCP>
Organization: Ask Computer Systems, Ingres Products Division
Lines: 13

In article <15458@uswat.UUCP> ilene@zeb.USWest.COM () writes:
>...
> back to the drawing board.  Anybody out there know how to find out
> about  the status of a particular child process at any given time in 
> the program.  Thanks .
>
> Ilene

Why not spawn off a thread that does nothing but DosCwait for children?
You can arrange with RAM semaphores so that is only waits when there
are one or more processes outstanding.

	-scott e. garfinkle