Hey
How to stop rough processes under Gloira?
Programs that dies or stop function properly may leave processes behind that can't be killed by any means. Not even the supposable unblockable kill kill command works. Since I also run a non Ubuntu based system (VectorLinux) I know that this issue is Ubuntu related.
My question is how to deal with this kind of rough processes? Is it possible to make the kill kill command really kill as it should?
Thanks...
How to kill what can't be killed ?
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
How to kill what can't be killed ?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: How to kill what can't be killed ?
Can you give an example? The kill command has never failed for me.
Re: How to kill what can't be killed ?
Kaye wrote:
Last time it happens for me it was Nautilus who left behind a process that ignored any attempt to kill it.
The problem is not connected to any particular program or even Gloria. I used Kubuntu earlier with same issue.Can you give an example? The kill command has never failed for me.
Last time it happens for me it was Nautilus who left behind a process that ignored any attempt to kill it.
Re: How to kill what can't be killed ?
Could you please explain "kill kill"?
I am familiar with "kill", and "killall", but "kill kill" confuses me!
I am familiar with "kill", and "killall", but "kill kill" confuses me!
-
- Level 5
- Posts: 526
- Joined: Sat Jul 14, 2007 11:31 am
Re: How to kill what can't be killed ?
More helpfully, could you take a screenshot of your System Monitor and show us what these immortal processes are?
Re: How to kill what can't be killed ?
Missed wrote:
red-e-made wrote:
Sorry, meant sending signal 9 SIGKILL to the process. It should be unblockable but under Ubuntu this is not the case.Could you please explain "kill kill"?
I am familiar with "kill", and "killall", but "kill kill" confuses me!
red-e-made wrote:
More helpfully, could you take a screenshot of your System Monitor and show us what these immortal processes are?
[/qutoe]
Would like to do that but the problem is not related to any particular kind of process and I can't generate the problem by will. I simply don't know why it happens just that it do.
The only solution is to shutdown the system and this might not even work due the rough process. The system ends up waiting for the process to finish. Manual reset is then the only option as far as I know.
Re: How to kill what can't be killed ?
Are you talking about zombie processes? I don't think those can be killed, but they don't take up any resources anyway so it shouldn't be a problem.
I just checked and I have a zombie claws-mail thread that can't be removed with sudo kill -9 but it's not doing anything and Claws Mail still works.
I just checked and I have a zombie claws-mail thread that can't be removed with sudo kill -9 but it's not doing anything and Claws Mail still works.
Re: How to kill what can't be killed ?
Hmmm....
I would have guessed that this was a rather well known issue. But as it looks this not the case. So lets tackle this with a different angel.
If I get a rough process as described above, how do I analyse it?
The process table identify the process but does not explain why it can't be terminated. My question is what should I next? How do I find more information? A good place to start, I guess, is in the process folder (/proc/xxxx) but where do I look and for what? Since the process may not be the problem it self but merely a sign of a deeper problem how do I do then?
The problem I have with rough processes is mainly:
Thanks for any ideas...
I would have guessed that this was a rather well known issue. But as it looks this not the case. So lets tackle this with a different angel.
If I get a rough process as described above, how do I analyse it?
The process table identify the process but does not explain why it can't be terminated. My question is what should I next? How do I find more information? A good place to start, I guess, is in the process folder (/proc/xxxx) but where do I look and for what? Since the process may not be the problem it self but merely a sign of a deeper problem how do I do then?
The problem I have with rough processes is mainly:
- It may stop one from using an application. It can't be started again.
- It may take so much of the system resources that the system can no longer be used.
- It may prevent the system shutting down properly forcing manual reset.
Thanks for any ideas...
-
- Level 5
- Posts: 526
- Joined: Sat Jul 14, 2007 11:31 am
Re: How to kill what can't be killed ?
Not to sound like a broken record: I know you can't will it to happen, but if the next time this happens you could take a screenshot of the Processes tab of your System Monitor, that could go a long way in getting to the root of this problem.