Xref: utzoo comp.unix.questions:11766 comp.unix.wizards:14753 comp.unix.xenix:5041
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!xanth!nic.MR.NET!hal!ncoast!allbery
From: allbery@ncoast.ORG (Brandon S. Allbery)
Newsgroups: comp.unix.questions,comp.unix.wizards,comp.unix.xenix
Subject: Re: Getting rid of a <defunct> process
Message-ID: <13390@ncoast.ORG>
Date: 18 Feb 89 01:36:29 GMT
References: <102@avatar.UUCP>
Reply-To: allbery@ncoast.UUCP (Brandon S. Allbery)
Followup-To: comp.unix.questions
Distribution: usa
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 18

As quoted from <102@avatar.UUCP> by kory@avatar.UUCP (Kory Hamzeh):
+---------------
| I have written an application which forks and execs off many subtasks.
| The main process (the parent which does all of the forks) can not
| do a wait() because I can't get blocked for anything. Well, this results
| in a lot of "<defunct>" processes in the process table when the child
| exits.
+---------------

Add a call to signal(SIGCLD, SIG_IGN).  This tells the system to not leave
zombies around for child processes.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser