Date: Tue, 09 Jul 1996 20:55:52 -0700 From: "Michael L. VanLoon -- HeadCandy.com" <michaelv@HeadCandy.com> To: Brandon Gillespie <brandon@tombstone.sunrem.com> Cc: freebsd-hackers@freebsd.org Subject: Re: handling SIGCHLD with multiple children Message-ID: <199607100355.UAA20203@MindBender.HeadCandy.com> In-Reply-To: Your message of Tue, 09 Jul 96 12:26:35 -0600. <Pine.BSF.3.91.960709122409.4725A-100000@tombstone.sunrem.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>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.
-----------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607100355.UAA20203>