Click to See Complete Forum and Search --> : can't kill a task
moose
01-19-2001, 03:56 PM
I tried to erase all the data on a floppy and went into the floppy and ran "rm *"
Now I can't stop the rm process. Can't kill, can't do anything to it. Any ideas? I'd rather not reboot my machine...looking to stop the rm command that has the CPU pinned!
Edit:
I've tried to kill the task from ktop, and also killing the PID with the kill command itself. No luck.
Moose
[This message has been edited by moose (edited 19 January 2001).]
andrzej
01-19-2001, 04:05 PM
http://www.linuxnewbie.org/ubb/confused.gif
You can't even 'kill -9' ?!
http://www.linuxnewbie.org/ubb/eek.gif
moose
01-19-2001, 04:07 PM
what's the syntax for kill -9? I mean...I did a "Kill 16067" (16067 is the PID) How would I incorporate the -9 into that?
andrzej
01-19-2001, 04:10 PM
kill -9 16067
Strike
01-19-2001, 04:10 PM
kill -9 16067
or
killall -KILL rm
would work as well, I think.
moose
01-19-2001, 04:14 PM
uh....nope...didn't work...any other ideas??? My poor poor processor has been running HARD for about 40 mins now!
veloctTX
01-19-2001, 05:07 PM
try running gps, see if you can kill it with that option. I would think not since the commands didn't take before.
Dru Lee Parsec
01-19-2001, 05:21 PM
DOOD! U R SO SCREWED!
An rm * should only be erasing things in the directory where you ran that command. If that's a floppy then there really shouldn't be much there. So, if it's been running for over half an hour then you may be erasing your hard drive (I don't see you you could though. You ran rm * in /mnt/floppy correct?)
One last way to kill a task. Switch to root by doing an "su" in terminal window. run "top" and see what the task is. When you see the PID number then type "k" to kill then the ID number (and enter) and then the number "9". This should kill the task.
Type a "q" to get out of top.
moose
01-19-2001, 11:45 PM
Thanks for your help everyone....in the end nothing worked...I had to...sniff......after 227 days of uptime....sniff....reboot.
Oh well....
Thanks again!
MBMarduk
01-19-2001, 11:56 PM
Holy sh*t! You spent all these hours waiting for the fscking floppy-LED to die?
Ok, uptimes are cool, just don't let'em give U a heart attack, man!
**Sends positive vibez to victim**
Peace, dude.
Gents:
This rogue "floppy" process crap does NOT impress me. Maybe you could'a taken out the floppy ... with a potholder.
Now for REAL rogues, I once had a processs on an SGI_IRIS so tuff-ta-kill that to zap it, I had to sprinkle holy water on the keyboard, AFTER cutting the powercord with a penknife, dumping liquid nitrogen on the HD AND driving a screwdriver thru the SKY_coprocessor board.
Just proves modern weenies are wimps.