From owner-freebsd-hackers Tue Jul 9 20:56:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA03919 for hackers-outgoing; Tue, 9 Jul 1996 20:56:17 -0700 (PDT) Received: from MindBender.HeadCandy.com (root@mindbender.headcandy.com [199.238.225.168]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA03913 for ; Tue, 9 Jul 1996 20:56:12 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.HeadCandy.com (8.7.5/8.7.3) with SMTP id UAA20203; Tue, 9 Jul 1996 20:55:53 -0700 (PDT) Message-Id: <199607100355.UAA20203@MindBender.HeadCandy.com> X-Authentication-Warning: MindBender.HeadCandy.com: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Brandon Gillespie cc: freebsd-hackers@freebsd.org Subject: Re: handling SIGCHLD with multiple children In-reply-to: Your message of Tue, 09 Jul 96 12:26:35 -0600. Date: Tue, 09 Jul 1996 20:55:52 -0700 From: "Michael L. VanLoon -- HeadCandy.com" 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? What about using pipes and select? ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@HeadCandy.com --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... Roll your own Internet access -- Seattle People's Internet cooperative. If you're in the Seattle area, ask me how. -----------------------------------------------------------------------------