* Re: [gentoo-user] Die, process! Die!
2006-10-30 15:01 [gentoo-user] Die, process! Die! Michael Sullivan
@ 2006-10-30 15:13 ` fire-eyes
2006-10-30 15:30 ` Arnau Bria
` (4 subsequent siblings)
5 siblings, 0 replies; 14+ messages in thread
From: fire-eyes @ 2006-10-30 15:13 UTC (permalink / raw
To: gentoo-user
Michael Sullivan wrote:
> I know my subject line is a little melodramatic, but this is really
> frustrating. I frequently have processes that killall doesn't kill and
> kill -9 <pid> doesn't touch. For instance, this is taken from top:
>
> 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
>
> I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> killall javadocs and kill -9 24135 and still it runs. Is there a way of
> getting rid of this process short of rebooting the machine?
>
do a pstree, and find its parent, and kill that. if that doesn't work
kill the parents parent. Note that any parent you kill, kills the
children, too (god this sounds wrong). If it's init... reboot.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-30 15:01 [gentoo-user] Die, process! Die! Michael Sullivan
2006-10-30 15:13 ` fire-eyes
@ 2006-10-30 15:30 ` Arnau Bria
2006-10-30 23:35 ` Iain Buchanan
` (3 subsequent siblings)
5 siblings, 0 replies; 14+ messages in thread
From: Arnau Bria @ 2006-10-30 15:30 UTC (permalink / raw
To: gentoo-user
On Mon, 30 Oct 2006 09:01:12 -0600
Michael Sullivan wrote:
> I know my subject line is a little melodramatic, but this is really
> frustrating. I frequently have processes that killall doesn't kill
> and kill -9 <pid> doesn't touch. For instance, this is taken from
> top:
killall = kill
The only diff is: killall - kill processes by name
Maybe processes are in a state where signals could not be
delivered, and you must wait until that state change...
If you want to see what signals a process is waiting for, you could use
ps.
Cheers!
--
Arnau Bria
http://blog.emergetux.net
Wiggum: Dispara a las ruedas Lou.
Lou: eee, es un tanque jefe.
Wiggum: Me tienes hartito con todas tus excusas.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-30 15:01 [gentoo-user] Die, process! Die! Michael Sullivan
2006-10-30 15:13 ` fire-eyes
2006-10-30 15:30 ` Arnau Bria
@ 2006-10-30 23:35 ` Iain Buchanan
2006-10-31 0:34 ` Michael Sullivan
2006-10-31 2:33 ` Henk Boom
` (2 subsequent siblings)
5 siblings, 1 reply; 14+ messages in thread
From: Iain Buchanan @ 2006-10-30 23:35 UTC (permalink / raw
To: gentoo-user
On Mon, 2006-10-30 at 09:01 -0600, Michael Sullivan wrote:
> I know my subject line is a little melodramatic, but this is really
> frustrating. I frequently have processes that killall doesn't kill and
> kill -9 <pid> doesn't touch. For instance, this is taken from top:
>
> 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
>
> I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> killall javadocs and kill -9 24135 and still it runs. Is there a way of
> getting rid of this process short of rebooting the machine?
I assume you did kill and killall as root?
--
Iain Buchanan <iaindb at netspace dot net dot au>
It's the thought, if any, that counts!
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-30 23:35 ` Iain Buchanan
@ 2006-10-31 0:34 ` Michael Sullivan
0 siblings, 0 replies; 14+ messages in thread
From: Michael Sullivan @ 2006-10-31 0:34 UTC (permalink / raw
To: gentoo-user
On Tue, 2006-10-31 at 09:05 +0930, Iain Buchanan wrote:
> On Mon, 2006-10-30 at 09:01 -0600, Michael Sullivan wrote:
> > I know my subject line is a little melodramatic, but this is really
> > frustrating. I frequently have processes that killall doesn't kill and
> > kill -9 <pid> doesn't touch. For instance, this is taken from top:
> >
> > 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
> >
> > I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> > killall javadocs and kill -9 24135 and still it runs. Is there a way of
> > getting rid of this process short of rebooting the machine?
>
> I assume you did kill and killall as root?
> --
> Iain Buchanan <iaindb at netspace dot net dot au>
>
> It's the thought, if any, that counts!
>
Yes. I always do kill and killall with root.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-30 15:01 [gentoo-user] Die, process! Die! Michael Sullivan
` (2 preceding siblings ...)
2006-10-30 23:35 ` Iain Buchanan
@ 2006-10-31 2:33 ` Henk Boom
2006-10-31 2:48 ` Richard Fish
2006-10-31 7:36 ` Martins Steinbergs
5 siblings, 0 replies; 14+ messages in thread
From: Henk Boom @ 2006-10-31 2:33 UTC (permalink / raw
To: gentoo-user
On 30/10/06, Michael Sullivan <michael@espersunited.com> wrote:
> I know my subject line is a little melodramatic, but this is really
> frustrating. I frequently have processes that killall doesn't kill and
> kill -9 <pid> doesn't touch. For instance, this is taken from top:
>
> 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
>
> I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> killall javadocs and kill -9 24135 and still it runs. Is there a way of
> getting rid of this process short of rebooting the machine?
I remember having troubles doing ctr-C on mounts which I knew were
going to time out, and I was told that you couldn't kill it while it
was inside a kernel call or something to that effect. Of course, I
would thing that mount is going to get tied up in kernel stuff much
more often than something like javadoc, so I really don't know if it's
the same sort of problem.
Hope this helps
Henk Boom
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-30 15:01 [gentoo-user] Die, process! Die! Michael Sullivan
` (3 preceding siblings ...)
2006-10-31 2:33 ` Henk Boom
@ 2006-10-31 2:48 ` Richard Fish
2006-10-31 7:33 ` Greg Bur
2006-11-03 4:44 ` Walter Dnes
2006-10-31 7:36 ` Martins Steinbergs
5 siblings, 2 replies; 14+ messages in thread
From: Richard Fish @ 2006-10-31 2:48 UTC (permalink / raw
To: gentoo-user
On 10/30/06, Michael Sullivan <michael@espersunited.com> wrote:
> I know my subject line is a little melodramatic, but this is really
> frustrating. I frequently have processes that killall doesn't kill and
> kill -9 <pid> doesn't touch. For instance, this is taken from top:
>
> 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
The only case that kill -9 doesn't work is if the process is locked up
in a kernel call. What is this process doing...accesing network files
per chance?
> I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> killall javadocs and kill -9 24135 and still it runs. Is there a way of
> getting rid of this process short of rebooting the machine?
If -9 doesn't work, it means your kernel is hungup, and yeah, you'll
have to reboot to fix.
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-31 2:48 ` Richard Fish
@ 2006-10-31 7:33 ` Greg Bur
2006-11-03 4:44 ` Walter Dnes
1 sibling, 0 replies; 14+ messages in thread
From: Greg Bur @ 2006-10-31 7:33 UTC (permalink / raw
To: gentoo-user
On 10/30/06, Richard Fish <bigfish@asmallpond.org> wrote:
> On 10/30/06, Michael Sullivan <michael@espersunited.com> wrote:
> > I know my subject line is a little melodramatic, but this is really
> > frustrating. I frequently have processes that killall doesn't kill and
> > kill -9 <pid> doesn't touch. For instance, this is taken from top:
> >
> > 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
>
> The only case that kill -9 doesn't work is if the process is locked up
> in a kernel call. What is this process doing...accesing network files
> per chance?
>
> > I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> > killall javadocs and kill -9 24135 and still it runs. Is there a way of
> > getting rid of this process short of rebooting the machine?
>
> If -9 doesn't work, it means your kernel is hungup, and yeah, you'll
> have to reboot to fix.
>
> -Richard
> --
I seem to remember seeing a utility called zkill at packetstorm once
that was intended to kill "zombie" processes. I'm not sure if this is
what you are encountering but you might want to give it a look. It
should be noted that zkill is one of those YMMV use-at-your-own-risk
type utilities and I'm not even sure if it will work with recent
kernels but it might be worth taking a look at.
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-31 2:48 ` Richard Fish
2006-10-31 7:33 ` Greg Bur
@ 2006-11-03 4:44 ` Walter Dnes
2006-11-03 7:09 ` Alan McKinnon
1 sibling, 1 reply; 14+ messages in thread
From: Walter Dnes @ 2006-11-03 4:44 UTC (permalink / raw
To: gentoo-user
On Mon, Oct 30, 2006 at 07:48:58PM -0700, Richard Fish wrote
> If -9 doesn't work, it means your kernel is hungup, and yeah, you'll
> have to reboot to fix.
Where does kill -15 fit in?
--
Walter Dnes <waltdnes@waltdnes.org> In linux /sbin/init is Job #1
My musings on technology and security at http://techsec.blog.ca
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-11-03 4:44 ` Walter Dnes
@ 2006-11-03 7:09 ` Alan McKinnon
2006-11-03 18:39 ` Richard Fish
0 siblings, 1 reply; 14+ messages in thread
From: Alan McKinnon @ 2006-11-03 7:09 UTC (permalink / raw
To: gentoo-user
On Friday 03 November 2006 06:44, Walter Dnes wrote:
> On Mon, Oct 30, 2006 at 07:48:58PM -0700, Richard Fish wrote
>
> > If -9 doesn't work, it means your kernel is hungup, and yeah,
> > you'll have to reboot to fix.
>
> Where does kill -15 fit in?
signal 15 is SIGTERM, and the default for kill. The thread is about
unkillable processes, meaning those that don't go away with kill or
kill -15
alan
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-11-03 7:09 ` Alan McKinnon
@ 2006-11-03 18:39 ` Richard Fish
2006-11-03 19:02 ` Michael Sullivan
0 siblings, 1 reply; 14+ messages in thread
From: Richard Fish @ 2006-11-03 18:39 UTC (permalink / raw
To: gentoo-user
On 11/3/06, Alan McKinnon <alan@linuxholdings.co.za> wrote:
> On Friday 03 November 2006 06:44, Walter Dnes wrote:
> > On Mon, Oct 30, 2006 at 07:48:58PM -0700, Richard Fish wrote
> >
> > > If -9 doesn't work, it means your kernel is hungup, and yeah,
> > > you'll have to reboot to fix.
> >
> > Where does kill -15 fit in?
>
> signal 15 is SIGTERM, and the default for kill. The thread is about
> unkillable processes, meaning those that don't go away with kill or
> kill -15
Just to expand on this a bit...
SIGTERM can be caught, blocked, or ignored by a process. It is
basically asking the _process_ to "quit now!".
SIGKILL cannot be caught, blocked, or ignored by a process. In fact,
no user-space code is even executed for SIGKILL. It is basically a
request to the kernel to "wipe this thing from memory!".
So if SIGKILL doesn't work, that usually means that the process has
allocated some resource in the kernel that now cannot be freed. An
example would be files open on an NFS server (mounted with the 'hard'
option), with dirty buffers needing to be flushed, but the NFS server
cannot be reached. SIGKILL would attempt to close those files, which
would attempt to flush out those buffers, which would not work.
Another example would be a buggy driver and a hung device (seen this
with ipw3945d on my own system!)
-Richard
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-11-03 18:39 ` Richard Fish
@ 2006-11-03 19:02 ` Michael Sullivan
2006-11-03 19:28 ` Petr Uzel
0 siblings, 1 reply; 14+ messages in thread
From: Michael Sullivan @ 2006-11-03 19:02 UTC (permalink / raw
To: gentoo-user
On Fri, 2006-11-03 at 11:39 -0700, Richard Fish wrote:
> On 11/3/06, Alan McKinnon <alan@linuxholdings.co.za> wrote:
> > On Friday 03 November 2006 06:44, Walter Dnes wrote:
> > > On Mon, Oct 30, 2006 at 07:48:58PM -0700, Richard Fish wrote
> > >
> > > > If -9 doesn't work, it means your kernel is hungup, and yeah,
> > > > you'll have to reboot to fix.
> > >
> > > Where does kill -15 fit in?
> >
> > signal 15 is SIGTERM, and the default for kill. The thread is about
> > unkillable processes, meaning those that don't go away with kill or
> > kill -15
>
> Just to expand on this a bit...
>
> SIGTERM can be caught, blocked, or ignored by a process. It is
> basically asking the _process_ to "quit now!".
>
> SIGKILL cannot be caught, blocked, or ignored by a process. In fact,
> no user-space code is even executed for SIGKILL. It is basically a
> request to the kernel to "wipe this thing from memory!".
>
> So if SIGKILL doesn't work, that usually means that the process has
> allocated some resource in the kernel that now cannot be freed. An
> example would be files open on an NFS server (mounted with the 'hard'
> option), with dirty buffers needing to be flushed, but the NFS server
> cannot be reached. SIGKILL would attempt to close those files, which
> would attempt to flush out those buffers, which would not work.
> Another example would be a buggy driver and a hung device (seen this
> with ipw3945d on my own system!)
>
> -Richard
So how would I issue a SIGKILL?
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-11-03 19:02 ` Michael Sullivan
@ 2006-11-03 19:28 ` Petr Uzel
0 siblings, 0 replies; 14+ messages in thread
From: Petr Uzel @ 2006-11-03 19:28 UTC (permalink / raw
To: gentoo-user
Dne pátek 03 listopad 2006 20:02 Michael Sullivan napsal(a):
> So how would I issue a SIGKILL?
All of these should work with the same effect :
kill -SIGKILL pid
kill -KILL pid
kill -9 pid
Alternatively, you could also use
killall -9 progname
if you know only name of the program but not its pid.
Regards,
--
Petr Uzel
petr.uzel@centrum.cz
Jabber : knotor@njs.netlab.cz
ICQ : 101606095
Gentoo Linux
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Die, process! Die!
2006-10-30 15:01 [gentoo-user] Die, process! Die! Michael Sullivan
` (4 preceding siblings ...)
2006-10-31 2:48 ` Richard Fish
@ 2006-10-31 7:36 ` Martins Steinbergs
5 siblings, 0 replies; 14+ messages in thread
From: Martins Steinbergs @ 2006-10-31 7:36 UTC (permalink / raw
To: gentoo-user
On Monday 30 October 2006 17:01, Michael Sullivan wrote:
> I know my subject line is a little melodramatic, but this is really
> frustrating. I frequently have processes that killall doesn't kill and
> kill -9 <pid> doesn't touch. For instance, this is taken from top:
>
> 24135 root 16 0 229m 35m 1064 S 0.3 59.7 8:52.11 javadoc
>
> I have Cntrl+C on the emerge (five minutes ago) and I've issued multiple
> killall javadocs and kill -9 24135 and still it runs. Is there a way of
> getting rid of this process short of rebooting the machine?
never checked what the difference under the hood, however try
fuser -k javadoc
m
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 14+ messages in thread