Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpda!hpdslab!hpiacla!marki
From: marki@hpiacla.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Setting process groups
Message-ID: <4070007@hpiacla.HP.COM>
Date: Thu, 3-Dec-87 17:43:36 EST
Article-I.D.: hpiacla.4070007
Posted: Thu Dec  3 17:43:36 1987
Date-Received: Thu, 10-Dec-87 03:07:19 EST
References: <910@mcgill-vision.UUCP>
Organization: HP Industrial Applications Center (IAC)
Lines: 20

One method I've used for a parent killing children but not the parent
itself is to set up the parent as the process group leader.  Then the
parent spawns off some children.  The parent is then set to ignore a
signal, say signal 15.

Then have the parent issue a   kill (0, 15);  .  This will kill 
all processes in the process group including the parent.  However,
since the parent set itself up to ignore the signal, it will survive
the signal.  And live on to spawn another day (or child).


Mark

**************************************************************************
* Mark Ikemoto 	            | {ucbvax,hplabs}!hpda!hpiacla!marki  [UUCP] *
* Indus. Appl. Center (IAC) | mark@hpiacla                        [SMTP] *
* Hewlett-Packard Co.       | (408) 746-5453                      [AT&T] *
* 1266 Kifer Road           | 1-746-5453                     [HP-TELNET] *
* Sunnyvale, CA  94086      | "What If..."                [HP-TELEPATHY] *
**************************************************************************