On Sat, Feb 14, 2004 at 06:53:44AM -0500, [EMAIL PROTECTED] wrote:
Taking Chris' question further... why not implement wait queues (I'm
thinking along the lines of NT). Any session could declare it's interest
on a waitable object... and anyone with a reference to that object could
call
On (02/14 06:53), [EMAIL PROTECTED] wrote:
Taking Chris' question further... why not implement wait queues (I'm
thinking along the lines of NT).
+1 on wait queues. i think there are evil and wonderful things that
could be done with them.
--
Matt Cashner
http://eekeek.org
eek at eekeek dot org
Taking Chris' question further... why not implement wait queues (I'm
thinking along the lines of NT). Any session could declare it's interest
on a waitable object... and anyone with a reference to that object could
call wakeup on it. SIGCHLD handling is therefore just a special
case of this - you
On Fri, 13 Feb 2004 23:31:56 -0500 Rocco Caputo wrote:
+--
| Proposal: Registered PIDs.
|
| Currently SIGCHLD is broadcast to every session that registers a CHLD
| signal handler. Quite often, this means every session with child
| processes receives signals for every other
as long as the child's process id remains available in the current place you
won't break existing code like PoCo::Child so no objections here :)
-Original Message-
From: Rocco Caputo [mailto:[EMAIL PROTECTED]
Sent: Friday, February 13, 2004 8:32 PM
To: [EMAIL PROTECTED]
Subject: Proposal:
