Re: [LIP] SIGCHLD behaviour...

> If disposition of SIGCHLD has been set with signal or sigset, or sigaction
> and SA_NOCLDSTOP flag has been
> set, it will only be sent to the calling process when its children exit.
> If not set, SIGCHLD is sent also when the calling process' children are
> stopped or continued due to job control.
> 
> Does Linux kernel have a different behaviour for SIGCHLD? In a concurrent
In linux, SIGCHLD is handled specially. If you want the kernel to clean up
the terminated children, the parent must explicitlyset the action to ignore.
Else, even though the default action is ignore, it will never b e delivered
to the process. And init will have to take care fo zonbies and other
children.



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click