Operating Systems > Linux and UNIX

killing things

(1/3) > >>

Master of Reality:
I ran rmmod and it wont stop. I tried to kill it but it wouldnt stop. How woul i go about forcing something to die?

voidmain:
Did you try pressing on the brake pedal?

Seriously, "rmmod" is for removing kernel modules, not for killing processes.  "kill" is for killing, stopping, or sending other signals to processes that are running.  If a "kill -9 PID" (where PID is the Process ID number) as root won't kill something then there could be several reasons. Usually it's a "defunct" (also known as "zombie") process.

Sometimes programs/daemons will spawn a child process which when killed or dies sometimes will not get properly cleaned up by the parent process (poorly written apps sometimes are the cause). Trying to kill the zombie child process may prove fruitless, but if you kill/stop the parent process the zombie should also disappear.

Also I have seen times if you try to kill a process that is in the act of performing I/O on removeable media that may be damaged it can hang the process and appear not to die. In those cases I find that manually ejecting the media allows the program to exit. I am sure there are more that I can think of. Most of the time killing or restarting the parent will fix you up though.

Don't know if this is what you are after. It's really hard to tell with the very limited information you gave, like what process you were trying to kill and what the process was doing when you tried to kill it.

Master of Reality:
i was using rmmod to remove the ipchains module (After flushing and stoppping ipchains).
rmmod wont stop trying to take out ipchains. It isnt taking up very many resources so i am doubting whether it even started rmoving the ipchains module. I tried to kill rmmod but it wouldnt stop.
rmmod has been running for about 30 min.

[ September 30, 2002: Message edited by: The Master of Reality / Bob ]

[ September 30, 2002: Message edited by: The Master of Reality / Bob ]

voidmain:
Ahh, in this case it would be a little different as the kernel or kernel module itself would be the "parent". Kind of hard to kill the kernel. I assume you closed the window or exited the session that you ran the rmmod command from and it still exists? This would likely be a poorly written module or some sort of kernel bug. What module are you trying to unload?

Master of Reality:

quote:Originally posted by The Master of Reality / Bob:
i was using rmmod to remove the ipchains module

--- End quote ---


[ September 30, 2002: Message edited by: The Master of Reality / Bob ]

Navigation

[0] Message Index

[#] Next page