Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!bionet!agate!ucbvax!unisoft!greywolf From: greywolf@unisoft.UUCP (The Grey Wolf) Newsgroups: comp.unix.questions Subject: Re: Background processes on logout Message-ID: <3421@unisoft.UUCP> Date: 6 Mar 91 20:37:08 GMT References: <91051.180110F66204@BARILVM.BITNET> <1991Feb21.164300.3596@sbcs.sunysb.edu> <1991Feb22.035953.29266@athena.mit.edu> <1991Feb23.091836.14043@Think.COM> Reply-To: greywolf@unisoft.UUCP (The Grey Wolf) Organization: Foo Bar and Grill Lines: 34 <1991Feb23.091836.14043@Think.COM> by barmar@think.com (Barry Margolin) & In article <1991Feb22.035953.29266@athena.mit.edu> jik@athena.mit.edu (Jonathan I. Kamens) writes: & > I don't know if HP-UX supports the sending of a signal to "process" -1 in & >order to send it to all of the processes to which the user is allowed to send & >signals, but if it does, then you should be able to do "kill -1 -1" in your & >.logout file. & & Sounds like a good idea for a manual command, but not for a .logout file, & if you ever login on more than one terminal. If you're logged in twice and & use that command you'll kill all the processes on both terminals. Ah, but you see, "kill" is a csh builtin. So it will just kill off everything that is yours *except* the csh. The original request also seems to be unclear as to whether by backgrounded he means addressable as %2, %3, etc, or completely daemonized. If it's daemonized, then he should be a little more responsible about making sure that the programs check that the ppid is what it was when it started. I would give anything for the Pyramid OSx to have "kill -1" functionality in the kernel! & -- & Barry Margolin, Thinking Machines Corp. & & barmar@think.com & {uunet,harvard}!think!barmar -- # On the 'Net: Why are more and more fourth-level wizard(-wannabe)s trying # to invoke ninth-level magic instead of taking the time to climb the other # (quite essential) thirteen or fourteen levels so they can do this properly? # ...!{uunet,ucbvax}!unisoft!greywolf