Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!decuac!felix!zemon
From: gordon@prls.UUCP (Gordon Vickers)
Newsgroups: comp.unix.ultrix
Subject: killpg(2) fails (sometimes)
Message-ID: <10364@felix.UUCP>
Date: Sun, 25-Oct-87 20:07:04 EST
Article-I.D.: felix.10364
Posted: Sun Oct 25 20:07:04 1987
Date-Received: Wed, 28-Oct-87 02:57:14 EST
Sender: zemon@felix.UUCP
Lines: 31
Approved: zemon@felix.UUCP

Reply-Path:




     I am currently running 1.2 though I've had this problem since 1.0 .
     I have a very simple interface to the killpg(2) call but it fails
   if the parent process was started in rc.local  .

    Specifically, my application program xxx must run 24 hrs/day so,
   I have an appropriate entry in my /etc/rc.local to ensure it gets
   started.

     xxx is owned by root and has the setuid bit on.  Once started it
   spawns some number of children processes and then sleeps until all
   of the children have derminated.

     The killgp(2) call has worked flawlessly everytime except for those
   occations when xxx was started from /etc/rc.local .

     When the call fails, the error indicates that there is no such process.

     I have, of course, been the super user while using the call.

     Any help in resolving this would be most appreciated since killpg()
   provides the only easy-to-use way for shutting down my application.


 Gordon P. Vickers, (408) 991-5370,             =======================
 Signetics Corp.                                || Ultrix-32 ver 1.2 ||
 PO Box 3409  M/S 69                            ||     VAX 11/750    ||
 Sunnyvale, California,  USA  94086             =======================
 {pyramid, philabs}!prls!gordon
----- ALL DISCLAIMERS APPLY. In fact I have sent this whole mess by mistake.