Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 28 Nov 2007 14:55:34 +1100 (EST)
From:      Ian Smith <smithi@nimnet.asn.au>
To:        Alfred Perlstein <alfred@freebsd.org>
Cc:        freebsd-stable@freebsd.org, Honza Holakovsky <holakac@gmail.com>
Subject:   Re: Some processes stay active after killing its PID
Message-ID:  <Pine.BSF.3.96.1071128143745.7286E-100000@gaia.nimnet.asn.au>
In-Reply-To: <20071128015521.GO71382@elvis.mu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 27 Nov 2007, Alfred Perlstein wrote:
 > * Roland Smith <rsmith@xs4all.nl> [071127 11:59] wrote:
 > > On Tue, Nov 27, 2007 at 01:24:56PM -0600, Stephen Montgomery-Smith wrote:
 > > > 
 > > > 
 > > > On Tue, 27 Nov 2007, Honza Holakovsky wrote:
 > > > 
 > > >> Well, didn't know that, "/bin/kill -9 wdfs_PID" works, great
 > > >> 
 > > >> Thanks a lot, after your advice I read an article about csh built-in
 > > >> commands, never heard of it from any fbsd handbook...
 > > > 
 > > > I am completely baffled why this worked.  Why would /bin/kill -9 work when 
 > > > the built in csh kill -9 wouldn't?
 > > 
 > > According to the manual page for the built-in kill command, it
 > > recognizes 'kill -s 9', but not 'kill -9'.
 > 
 > Is it too late to remove csh from the base system? :D

:)  Whatever tcsh(1) may say, kill -9 (aka kill -KILL) has always worked
fine in csh here; I've never used kill -s.  I'm as baffled as Stephen. 

paqi% cat - &
[1] 5186
paqi% kill -9 5186
[1]    Killed                        cat -

Sure that's 'overkill', and that said, I've had processes that were
unkillable short of rebooting, including an errant mpd4 beta earlier
this year, when I certainly did try /bin/kill -9 too.  [5.5-STABLE]

Cheers, Ian




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.1071128143745.7286E-100000>