Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!csn!csn!arrayb!cwolff From: cwolff@intellistor.com (Clint Wolff) Subject: Re: SIGKILL and kill Message-ID: <1993Apr20.183620.301@intellistor.com> Keywords: SIGNALS SECURITY Organization: Intellistor, Longmont, CO References: <9304171535.ab08751@gate.demon.co.uk> <C5nsF8.35H@sugar.neosoft.com> <9304200033.af09432@gate.demon.co.uk> Date: Tue, 20 Apr 93 18:36:20 GMT Lines: 31 In article <9304200033.af09432@gate.demon.co.uk> damian@centrix.demon.co.uk (damian) writes: >In article <C5nsF8.35H@sugar.neosoft.com> peter@NeoSoft.com (Peter da Silva) writes: >>In article <9304171535.ab08751@gate.demon.co.uk> damian@centrix.demon.co.uk (damian) writes: >>> have seen a SIGKILL will soon follow. In fact I have been trying to >>> work out why sh ignores SIGTERM when at the command prompt (it behaves >>> properly when running a script). >> >>So you can do "kill 0" to get rid of background processes without logging out. > >Ah so there is a reason. Still I think that is a little inconsistent. After >all SIGTERM should mean "Please *you* die, and cleanup" (as opposed to the >SIGKILL's "Die sucker! Now!" :-)). Still I suppose I can't think of a better >signal that sh could use for the kill 0. > Actually, this is to avoid the unfortunate happenstance of hitting ^C to kill a program, waiting for it to die, getting bored, hitting ^C again, waiting... etc.. etc.. etc.. until the machine actually decides to kill it... Then, all the extra ^C's are fed into the shell which ignores them (rightfully so..) -- +-----------------------------------------------------------------------------+ | Clint Wolff Blonde and proud of it | | Fujitsu Computer Products of America - Intellistor Research and Development | | cwolff@slowboy.intellistor.com | +-----------------------------------------------------------------------------+ | SAVE BANDWIDTH... EMAIL YOUR RESPONSES TO THE PERSON WHO ASKED... | | DON'T POST ME-TO MESSAGES... EMAIL THE ORIGINAL POSTER FOR A SUMMARY | +-----------------------------------------------------------------------------+