Re: using of fork() in multithreaded application

> About zombies - this is a part of the lifetime of every process.
> When a process exits, it becomes a zombie.  [...]

> So you need to figure out why the parent isn't doing the wait().

Usually, yes.  But there's another possibility.

An exiting process does not always create a zombie.  It's possible to
set things up (eg, by the parent setting SIGCHLD to SIG_IGN) so that
the exiting process is reaped immediately instead of requiring someone
to wait for it.

Perhaps the parent is expecting this but things aren't set up correctly
to get that effect?

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		[email protected]
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B