[tkined] SIGCHLD vs fileevent
Christopher Akritides (foris@ans.net)
Fri, 24 Apr 1998 11:10:29 -0400 (EDT)
I have written a server that uses fileevent to listen to a socket for new
connections. It forks a child for every new connection and the child
handles the new socket input and exits. I have a trap handler in the
parent that catches SIGCHLD traps, so that the children don't become
zombies, but there is a problem. I would like the traps to be handled
immediately, even if there is a new socket request on the listening
socket. Instead, it seems like fileevents have a higher priorities than
SIGCHLD traps. Is that true? Is there a way around this, or should I just
slow down the rate of new connection requests? (I have control of the
clients too).
-----------------------------------------------------------------------------
Christopher Akritides Big Dial Development
(914) 701-5391 Page: 1-800-946-4646 1453477 ANS Communications
--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.