Re: [newbie] unkillable process?
Benjamin Pflugmann wrote: On Sun 2003-02-16 at 14:46:03 -0500, [EMAIL PROTECTED] wrote: Benjamin Pflugmann wrote: [...] Correct. If it does not, there is nothing a mere user (or admin) can do about it. I know it's late in the thread but I thought I'd mention that when I get a process that I can't kill from top or using ps then I've always had success doing it from webmin. haven't had one yet that couldn't be killed from webmin. Sorry to say so, but that makes no sense. webmin has not access to anything that kill or top hasn't. You made me curious enough that I installed webmin and had a look at the source and it uses the usual kill() system call as do the CLI kill and top. Really, if you observed this behaviour, I wonder why. You did use signal 9 (aka SIGKILL) when trying with kill/top, didn't you? Benjamin. Ben, Can't explain it and you're right when you say it doesn't have any access that isn't the same as ps or top, but as I said, I've not had a process yet that it couldn't get rid of when the others have failed. thats the simple fact of the experience. As for what signal was used...pretty much any and all. the fact that they wouldn't die was part of what led me to try webmin. I wasn't physically at the machine and ssh was a bit dodgey that day, so I connected to webmin and viola! no more nasty-refusing-to-die process. -- Mark --- Paid for by Penguins against modern appliances(R) Linux User Since 1996 Powered by Mandrake Linux 8.2 & 9.0 ICQ# 27816299 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] unkillable process?
Benjamin Pflugmann wrote: On Wed 2003-02-12 at 14:22:41 -0700, [EMAIL PROTECTED] wrote: [...] what i'm doing: ps ax | grep su (passwd) kill -s using all kinds of signals starting with sigterm, sigkill, Those two is all you need. "kill -s TERM" will ask the process to terminate (the process may refuse), "kill -s KILL" forcefully tries to kill the process (. If it doesn't terminate after a KILL signal, there is no way to do it. Usually it means that your kernel got a hickup which shouldn't normally happen. There are cases where the kernel cannot remove a process due to its internal state[1], but I only encountered these with either broken kernels (i.e. an update fixed it) or with broken hardware. signals like sigrtmin+2 even were [and man kill does not say]) man 7 signal (that's mentioned in "man kill") not wanting to get mucking around too much with something i didn't fully understand i didn't use them ALL but it seems like sigkill should kill just about anything :-/ Correct. If it does not, there is nothing a mere user (or admin) can do about it. I know it's late in the thread but I thought I'd mention that when I get a process that I can't kill from top or using ps then I've always had success doing it from webmin. haven't had one yet that couldn't be killed from webmin. -- Mark --- Paid for by Penguins against modern appliances(R) Linux User Since 1996 Powered by Mandrake Linux 8.2 & 9.0 ICQ# 27816299 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] unkillable process?
Thanks for some further explanation :) at least i can now understand what's going on anyway :) Jerry. On Wed, 12 Feb 2003 23:03:34 +0100 Benjamin Pflugmann <[EMAIL PROTECTED]> wrote: > On Wed 2003-02-12 at 14:22:41 -0700, [EMAIL PROTECTED] wrote: > [...] > > what i'm doing: > > ps ax | grep > > su > > (passwd) > > kill -s > > > > using all kinds of signals starting with sigterm, sigkill, > > Those two is all you need. "kill -s TERM" will ask the process to > terminate (the process may refuse), "kill -s KILL" forcefully tries to > kill the process (. > > If it doesn't terminate after a KILL signal, there is no way to do > it. Usually it means that your kernel got a hickup which shouldn't > normally happen. There are cases where the kernel cannot remove a > process due to its internal state[1], but I only encountered these with > either broken kernels (i.e. an update fixed it) or with broken > hardware. > > > signals like sigrtmin+2 even were [and man kill does not say]) > > man 7 signal > > (that's mentioned in "man kill") > > > not wanting to get mucking around too much with something i didn't > > fully understand i didn't use them ALL but it seems like sigkill > > should kill just about anything :-/ > > Correct. If it does not, there is nothing a mere user (or admin) can > do about it. > > HTH, > > Benjamin. > > > [1] AFAIK, a killed process which currently happens to be somewhere in > the "kernel space", will not terminate until it jumped back to > user space. So one explanation for such an unkillable process is > that it got stuck in the kernel space somehow. > -- -- Registered Linux user # 300600 Registered Linux machine # 185855 at http://counter.li.org (¬_ //\ V_/_ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] unkillable process?
On Wed 2003-02-12 at 14:22:41 -0700, [EMAIL PROTECTED] wrote: [...] > what i'm doing: > ps ax | grep > su > (passwd) > kill -s > > using all kinds of signals starting with sigterm, sigkill, Those two is all you need. "kill -s TERM" will ask the process to terminate (the process may refuse), "kill -s KILL" forcefully tries to kill the process (. If it doesn't terminate after a KILL signal, there is no way to do it. Usually it means that your kernel got a hickup which shouldn't normally happen. There are cases where the kernel cannot remove a process due to its internal state[1], but I only encountered these with either broken kernels (i.e. an update fixed it) or with broken hardware. > signals like sigrtmin+2 even were [and man kill does not say]) man 7 signal (that's mentioned in "man kill") > not wanting to get mucking around too much with something i didn't > fully understand i didn't use them ALL but it seems like sigkill > should kill just about anything :-/ Correct. If it does not, there is nothing a mere user (or admin) can do about it. HTH, Benjamin. [1] AFAIK, a killed process which currently happens to be somewhere in the "kernel space", will not terminate until it jumped back to user space. So one explanation for such an unkillable process is that it got stuck in the kernel space somehow. msg119277/pgp0.pgp Description: PGP signature
Re: [newbie] unkillable process?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 12 February 2003 04:22 pm, Jerry Barton wrote: > On Wed, 12 Feb 2003 14:33:07 -0500 > > Greg Meyer <[EMAIL PROTECTED]> wrote: > > > -- > > > > How are you killing the process? > > Greg, > thx for the reply :) > > what i'm doing: > ps ax | grep > su > (passwd) > kill -s > > using all kinds of signals starting with sigterm, sigkill, sigquit, > sigabrt... working my way through the signals until i finally just gave up > and rebooted (not knowing what some of the odd signals like sigrtmin+2 even > were [and man kill does not say]) not wanting to get mucking around too > much with something i didn't fully understand i didn't use them ALL but it > seems like sigkill should kill just about anything :-/ > Strange, as I've never had signal 9 (sigkill) not work for me. Although I always kill my pid's from within top. - -- Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+SsSTwDpHP6GALAARAjPrAJ9YPCwtrZ9EjovrjnfzlhUvc+8jMgCeO9oL g546PbxamAV4CPmAI4UaIpU= =+BNR -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [newbie] unkillable process?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 12 February 2003 01:25 pm, Jerry Barton wrote: > I had mozilla crash on me earlier this morning and when i tried to re-start > it i got that blasted mozilla profile picker thingy. i did ps ax | grep > mozilla and it came up with 6 mozilla processes. i killed them all BUT... > 2 of them would not die. i tried every signal i could think of to stop it > but it refused to be killed. I finally had to reboot. mplayer and xine > have both done this to me before too, come to think of it. to get mozilla > to work i've had to remove mozilla 1.1 and galeon and install mozilla 1.2.1 > from source, move my ~/.mozilla folder to ~/.mozilla-old, I STILL had to > create a new profile but at least mozilla is back up and running. (of > course... i can't install galeon now because it wants mozilla 1.1's mdk > rpm). Anyway... what to do about these semi immortal processes? > > Jerry > > -- How are you killing the process? - -- Greg -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+SqF0wDpHP6GALAARAnD6AJ4oRRFej4zNZBBHo8E8j6+g6/t0zgCeJhK+ C1g7RQRUAulqj2yOGfOMSkM= =Q79V -END PGP SIGNATURE- Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
[newbie] unkillable process?
I had mozilla crash on me earlier this morning and when i tried to re-start it i got that blasted mozilla profile picker thingy. i did ps ax | grep mozilla and it came up with 6 mozilla processes. i killed them all BUT... 2 of them would not die. i tried every signal i could think of to stop it but it refused to be killed. I finally had to reboot. mplayer and xine have both done this to me before too, come to think of it. to get mozilla to work i've had to remove mozilla 1.1 and galeon and install mozilla 1.2.1 from source, move my ~/.mozilla folder to ~/.mozilla-old, I STILL had to create a new profile but at least mozilla is back up and running. (of course... i can't install galeon now because it wants mozilla 1.1's mdk rpm). Anyway... what to do about these semi immortal processes? Jerry -- -- Registered Linux user # 300600 Registered Linux machine # 185855 at http://counter.li.org (¬_ //\ V_/_ Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
