Re: Event losing signals

>>>>> "MD" == Mark Dedlow <[email protected]> writes:

  MD> Event on my Redhat 8.0 linux system loses (doesn't get?) SIGCHLD's
  MD> that arrive too quickly.  I have a test script that works
  MD> correctly on Solaris, but not on Linux, so I'm guessing it's OS
  MD> specific?  Is this a known issue?

some OS's merge multiple duplicate signals into one delivery. you should
always do all the possible work you can when you get such a signal. that
means when you get a SIGCHLD, you try to reap all child procs until you
get no more. use a non-blocking waitpid option and a loop. i bet you are
reaping one child per signal you get.

never assume signal behavior is anything. it is such a poorly defined and
implemented API.

uri

-- 
Uri Guttman  ------  [email protected]  -------- http://www.stemsystems.com
----- Stem and Perl Development, Systems Architecture, Design and Coding ----
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org
Damian Conway Perl Classes - January 2003 -- http://www.stemsystems.com/class