[LIP] SIGCHLD behaviour...

I've a small query regarding SIGCHLD. The generic behaviour of SIGCHLD is as
follows:

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
server program, I never used SA_NOCLDSTOP flag while a lot many
children processes running where each child process serves an individual
connection.

Any comment?
-
sameer oak.


*********************************************************
Disclaimer:          

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com



-------------------------------------------------------
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