Re: [users] Unkillable process

2001-05-23 Thread MaD dUCK
also sprach Andrei Ivanov (on Tue, 22 May 2001 10:31:26PM -0500):
 scorpio   7314  0.0  3.8 2 4876 tty1 DMay10   0:00
 /usr/local/mozilla/mozilla-bin

this is a straight-forward failure of the linux kernel. it's a dead
process, it doesn't listen to anything anymore. there is no way you
can remove it without a reboot. the process is in uniterruptible
sleep state (implying it's doing some kind of i/o), but it's
definitely not interested in handling signals (even SIGKILL, which
you're the kernel isn't supposed to let you ignore). had plenty of
them, never succeeded without a reboot. but what do you care? just
leave them? they aren't eating anything away.

martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED]
-- 
prepBut nI vrbLike adjHungarian! qWhat's artThe adjBig nProblem?
   -- alec flett @netscape



Re: [users] Unkillable process

2001-05-23 Thread Paul D. Smith
%% MaD dUCK [EMAIL PROTECTED] writes:

  md also sprach Andrei Ivanov (on Tue, 22 May 2001 10:31:26PM -0500):
   scorpio   7314  0.0  3.8 2 4876 tty1 DMay10   0:00
   /usr/local/mozilla/mozilla-bin

  md this is a straight-forward failure of the linux kernel. it's a dead
  md process, it doesn't listen to anything anymore.

It's possible, under severe error conditions, to get processes which
won't respond to kill -9 on any kernel.  The KILL signal may not be
blocked by the process in user space, but that doesn't mean that it
can't be blocked by the kernel in kernel space, and it often is.

Simply whacking a process within the kernel at the instant you kill -9
would leave all sorts of resources unreleased, etc. etc.

Remember that when you kill a user process the kernel cleans up all its
memory, open file descriptors, etc. after it.  If you kill a process
within the kernel, who cleans up after that?  Thus, the kernel doesn't
allow processes to just disappear no matter what state they may be in
within the kernel itself.

-- 
---
 Paul D. Smith [EMAIL PROTECTED]HASMAT--HA Software Methods  Tools
 Please remain calm...I may be mad, but I am a professional. --Mad Scientist
---
   These are my opinions---Nortel Networks takes no responsibility for them.



Re: [users] Unkillable process

2001-05-23 Thread Andrei Ivanov
 also sprach Andrei Ivanov (on Tue, 22 May 2001 10:31:26PM -0500):
  scorpio   7314  0.0  3.8 2 4876 tty1 DMay10   0:00
  /usr/local/mozilla/mozilla-bin
 
 this is a straight-forward failure of the linux kernel. it's a dead
 process, it doesn't listen to anything anymore. there is no way you
 can remove it without a reboot. the process is in uniterruptible
 sleep state (implying it's doing some kind of i/o), but it's
 definitely not interested in handling signals (even SIGKILL, which
 you're the kernel isn't supposed to let you ignore). had plenty of
 them, never succeeded without a reboot. but what do you care? just
 leave them? they aren't eating anything away.

Thanks.
Problem is this:
now that I have a dead mozilla process in the background, netscape doesnt
want to run without manual interaction (when I run netscape as that user,
I'll have to manually kill a process that pops up because netscape saw a
mozilla process already running). It's not bad, but it gets kinda
messy after a while.
Andrei

--
First there was Explorer...
Then came Expedition.
This summer
Coming to a street near you..
Ford Exterminator.
--
Andrei Ivanov
http://arshes.dyndns.org
[EMAIL PROTECTED]
12402354
--



Re: [users] Unkillable process

2001-05-23 Thread Mario Olimpio de Menezes
On Wed, 23 May 2001, MaD dUCK wrote:

 also sprach Andrei Ivanov (on Tue, 22 May 2001 10:31:26PM -0500):
  scorpio   7314  0.0  3.8 2 4876 tty1 DMay10   0:00
  /usr/local/mozilla/mozilla-bin

 this is a straight-forward failure of the linux kernel. it's a dead

I believe this was corrected in kernel 2.4.4 as I got such process when
running 2.4.3 on a SMP machine.

BTW, only a reboot will kill such processes, as said bellow by MaD dUCK.


 process, it doesn't listen to anything anymore. there is no way you
 can remove it without a reboot. the process is in uniterruptible
 sleep state (implying it's doing some kind of i/o), but it's
 definitely not interested in handling signals (even SIGKILL, which
 you're the kernel isn't supposed to let you ignore). had plenty of
 them, never succeeded without a reboot. but what do you care? just
 leave them? they aren't eating anything away.

 martin;  (greetings from the heart of the sun.)
   \ echo mailto: !#^.*|tr * mailto:; [EMAIL PROTECTED]
 --
 prepBut nI vrbLike adjHungarian! qWhat's artThe adjBig nProblem?
-- alec flett @netscape


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




Mario O.de MenezesMany are the plans in a man's heart, but
IPEN-CNEN/SP is the Lord's purpose that prevails
http://curiango.ipen.br/~mario Prov. 19.21