Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!wuarchive!udel!haven!mimsy!chris
From: chris@mimsy.umd.edu (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: Can a parent process determine its child's status ?
Message-ID: <22945@mimsy.umd.edu>
Date: 7 Mar 90 04:51:50 GMT
References: <5090.25e135aa@mva.cs.liv.ac.uk> <2377@rex.cs.tulane.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 15

>In article <5090.25e135aa@mva.cs.liv.ac.uk> adh@mva.cs.liv.ac.uk writes:
>>Unfortunately, a [nonblocking] call to 'read' returns zero if the child
>>hasn't sent any new data *OR* [for EOF]....

In article <2377@rex.cs.tulane.edu> mb@rex.cs.tulane.edu (Mark Benard) writes:
>If you have BSD, you can use select instead of polling.

If you have BSD, a non-blocking read() will return -1 with errno set to
EWOULDBLOCK; an EOF returns 0 with errno unchanged.

Anyway, the original question (about detecting exited children) has already
been answered.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@cs.umd.edu	Path:	uunet!mimsy!chris