What is the most drastic way to kill a program?

**Bartman** · 09-03-2002, 04:37 PM

How can I kill a program that has locked up completely and doesnt seem to react to anything?

I tries these, but didnt work:
CTRL+C
kill -KILL <pid>
kill -TERM <pid>
kill -HUP <pid>

**cloverm** · 09-03-2002, 04:40 PM

I had this happen to me. The only command that worked was: reboot

**Schotty** · 09-03-2002, 05:39 PM

I take it you couldnt xkill it? That has worked for me when the cli wouldnt help.

**pbharris** · 09-03-2002, 05:46 PM

kill -9 PID ? also - are the parent processes dead?

**gorn** · 09-04-2002, 04:50 AM

you mean like mount /mnt/cdrom and not being able to kill it? mount and some other things to stuff in /dev can lock up beyond a ^C or kill -9.

**Bartman** · 09-04-2002, 08:07 PM

[quote author=gorn link=board=1;threadid=4840;start=0#48259 date=1031111410]
you mean like mount /mnt/cdrom and not being able to kill it? mount and some other things to stuff in /dev can lock up beyond a ^C or kill -9.
[/quote]

Wow, nice guess

It actually was modprobe ide-cd that locked up, with absolutely no way to kill it. I still don't see why it locked up. Could read the cdrom or so?
I think the reason why it couldn't be killed is probably because the modprobe program is somehow connected to the kernel, and obviously, you cant kill the kernel

**gorn** · 09-06-2002, 02:10 AM

[quote author=Bartman link=board=1;threadid=4840;start=0#48333 date=1031166460]I think the reason why it couldn't be killed is probably because the modprobe program is somehow connected to the kernel, and obviously, you cant kill the kernel

[/quote]

bingo

Yea, i've never seen modprobe hang... but i can see it more so than mount, and mount i've seen many times.

Reboot gets rid of it, if it happens everytime, something is screwy with your kernel.