Xref: utzoo comp.os.os2.misc:715 comp.os.os2.apps:94 comp.os.os2.programmer:466
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!uunet!panews.awdpa.ibm.com!ibmpa.awdpa.ibm.com!mikem
From: mikem@panews
Newsgroups: comp.os.os2.misc,comp.os.os2.apps,comp.os.os2.programmer
Subject: Re: knowing when a child process has died
Message-ID: <1991Feb20.173755.14036@ibmpa.awdpa.ibm.com>
Date: 20 Feb 91 17:37:55 GMT
References: <15458@uswat.UUCP>
Sender: news@ibmpa.awdpa.ibm.com (news id)
Reply-To: mikem@ibmpa.awdpa.ibm.com (Michael MacFaden)
Organization: IBM M&S Development, Palo Alto
Lines: 19

In article <15458@uswat.UUCP> ilene@zeb.USWest.COM () writes:
>
> I need to know how to determine when a particular child process has 
> died - at any given time in my program.  
>
> Ilene

Have the program create a System Semaphore. If the parent wants to
check if the child is still around, have it try to create the same
system semaphore (eg "\sem\child.sem"). There are other variations,
You could use shared memory, or install a signal handler, or use
a User message (if using PM).

Hope this gives you some ideas.

Regards,
Michael R. MacFaden    IBM Palo Alto     Marketing Systems
mikem@ibmpa.awdpa.ibm.com, macfaden@paloic1.iinus1.ibm.com 
disclaimer:...the usual...