Path: utzoo!attcan!utgpu!watmath!att!tut.cis.ohio-state.edu!pacific.mps.ohio-state.edu!gem.mps.ohio-state.edu!uwm.edu!mailrus!uflorida!novavax!hcx1!gerry
From: gerry@SSD.HARRIS.COM (Gerry Baumgartner)
Newsgroups: comp.unix.questions
Subject: Re: waitpid? (Was "Re: Converting wait3() to System V")
Keywords: waitpid
Message-ID: <1557@hcx1.UUCP>
Date: 20 Sep 89 17:54:52 GMT
References: <10800032@bradley> <434@ohs.UUCP> <439@lxn.eds.com>
Sender: news@hcx1.UUCP
Reply-To: gerry@hcx1.SSD.HARRIS.COM (Gerry Baumgartner)
Organization: Harris Computer Systems, Fort Lauderdale, FL
Lines: 21

In article <439@lxn.eds.com> bill@lxn.UUCP (Bill Doviak) writes:
>In article <434@ohs.UUCP> mday@ohs.UUCP (Matthew T. Day) writes:
>>
>>Try using waitpid().  You'll need to include <sys/wait.h>, if you haven't
>>          ^^^^^^^^^?
>
>What's that? It's not documented in my SysV R2 or SysV R3 manuals.

waitpid() is a routine specified by POSIX 1003.1.  It adds to wait() some of 
the functionality of wait3(), namely the use of wait3 options.  It also lets 
you specify a set of child processes for which status is requested, i.e. a
process with a specific pid or process group ID.  It's my understanding that it
will make it's appearance in SysV R4 or any OS thats going to be POSIX 1003.1
compliant. 

-------------------------------------------------------------------------------
Gerry Baumgartner                |    gerry@ssd.harris.com 
System Software Development      | or gerry%ssd.harris.com@eddie.mit.edu
Harris Computer Systems Division | or ...!{mit-eddie,uunet,novavax}!hcx1!gerry
Fort Lauderdale FL 33309         |
-------------------------------------------------------------------------------