From owner-freebsd-hackers Tue Jul 9 11:26:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA26344 for hackers-outgoing; Tue, 9 Jul 1996 11:26:46 -0700 (PDT) Received: from tombstone.sunrem.com (tombstone.sunrem.com [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA26339 for ; Tue, 9 Jul 1996 11:26:44 -0700 (PDT) Received: (from brandon@localhost) by tombstone.sunrem.com (8.6.12/8.6.12) id MAA04739; Tue, 9 Jul 1996 12:26:36 -0600 Date: Tue, 9 Jul 1996 12:26:35 -0600 (MDT) From: Brandon Gillespie To: freebsd-hackers@freebsd.org Subject: handling SIGCHLD with multiple children Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there _ANY_ way of finding what child sent a SIGCHLD signal to the parent process? I have a situation where a parent may have multiple children processing different tasks, and the parent is waiting for one child to complete a specific task, which it cares about, but it does not care about the other children. Because of this in most instances when SIGCHLD is received it simply resets it and continues working, except for now I need to handle things differently when a specific child sends SIGCHLD. Is there any ANY way to figure out where it came from? Thanks.. -Brandon