Path: utzoo!attcan!uunet!aplcen!samsung!usc!bbn!oliveb!mipos3!omepd!merlyn
From: merlyn@iwarp.intel.com (Randal Schwartz)
Newsgroups: comp.unix.questions
Subject: Re: core files under SV
Message-ID: <5236@omepd.UUCP>
Date: 20 Nov 89 21:15:24 GMT
References: <29843@iuvax.cs.indiana.edu>
Sender: news@omepd.UUCP
Reply-To: merlyn@iwarp.intel.com (Randal Schwartz)
Organization: Stonehenge; netaccess via Intel, Hillsboro, Oregon, USA
Lines: 22
In-reply-to: bobmon@iuvax.cs.indiana.edu (RAMontante)

In article <29843@iuvax.cs.indiana.edu>, bobmon@iuvax (RAMontante) writes:
| Um, I don't see why this "reaps the zombies".  I thought the `wait(pid)'
| call was added to clean up the aborted child --- here the child is
| wait()'ed on, but the grandchild looks just like the child did in the
| original version.

Ahhh, yes, but the grandchild is inherited by init, having been
orphan-ed by its parent.  The original process will not see the
grandchild as a potential child to be "wait"-ed for.

I don't like the presented code though, in that it will reap other
children that have not yet been wait-ed for.  There's no way around
that, though.  (Cursory glancing at the wait4() manpage under SunOS4
does not tell me if wait4() suffers from the same deficiency.  Anyone
know, offhand?  Mail please.)

Just another wait()-person,
-- 
/== Randal L. Schwartz, Stonehenge Consulting Services (503)777-0095 ====\
| on contract to Intel's iWarp project, Hillsboro, Oregon, USA, Sol III  |
| merlyn@iwarp.intel.com ...!uunet!iwarp.intel.com!merlyn	         |
\== Cute Quote: "Welcome to Oregon... Home of the California Raisins!" ==/