Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!pasteur!ucbvax!ucsfcgl!pixar!unicom!greywolf
From: greywolf@unicom.UUCP (if ($?NAME == 0) setenv NAME "`/u/select/greywolf/+bin/rndline /u/select/greywolf/+text/rndnames`")
Newsgroups: comp.unix.questions
Subject: Re: csh quick logout?
Keywords: kill -9 -1 works really nicely (read below before flaming)
Message-ID: <258@unicom.UUCP>
Date: 29 Jan 88 20:30:09 GMT
References: <20602@teknowledge-vaxc.ARPA>
Reply-To: greywolf@unicom.UUCP (Roan Anderson)
Organization: UNIx at College Of Marin, Kentfield, CA
Lines: 29
Whaddya-want-for-nothing: Rubba Beeskeet?

In article <20602@teknowledge-vaxc.ARPA> mkhaw@teknowledge-vaxc.ARPA (Mike Khaw) writes:
>Is there a clean way -- other than using "jobs", then "kill", then
>{^D,exit,logout} -- to force a quick logout that will kill off your
>stopped jobs?

>For example, can you be sure that "kill -HUP 0" will make your stopped
>jobs terminate as well?  We've had people disconnect from the system
>(my guess is via "kill -KILL $$") and litter the system with stopped
>gnu-emacses and stopped-informix-sqls and whatnot.

Has anyone out there ever tried kill -1 -1; followed by kill -9 -1?
If used as a csh builtin, kill -$WHATEVER -1 will send a $WHATEVER signal to
every process on the system that is running as you *except* the shell it
was called from.  If used as /bin/kill, it will kill ALL processes on the
system belonging to you.  As you might guess, it is not wise to do a
/bin/kill -1 -1 if you are root... :-)

This is on 4.x BSD; but from what I saw of system V, it should work there
too.  I have found it extremely handy, especially with runaway processes that
know no bounds...


Roan (looks strange, sounds like "Rowan" as in Rowan & Martin) Anderson

-- 
 " <- (2 dots)		    ::   / | \ ...!{sun,ucbvax}!pixar!unicom!greywolf
Roan Anderson, Local Guru   ::  :  |  :
(which doesn't say much)    ::  : /|\ : war: Invalid argument.
:::::::::::::::::::::::::::::::: =_|_=  ::::::::::::::::::::::::::::::::::::::