All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Langås" <tlan@stud.ntnu.no>
To: linux-kernel@vger.kernel.org
Subject: Unable to kill processes in D-state
Date: Sat, 5 Oct 2002 11:07:05 +0200	[thread overview]
Message-ID: <20021005090705.GA18475@stud.ntnu.no> (raw)

Hi!

We have a fairly large installation on-campus, and we have some problems
with the current linux-kernel (and older ones) - namely that processes
entering D-state will stay there forever (given that the right event got
them there in the first place).  This right event is killing the 
autofs-daemon.  Doing this will result in heavy load because of lots
of D-state processes, and you can't kill any of the D-state processes.
Why shouldn't one be able to kill processes that has entered D-state?
We have to reboot our servers to get rid of this problem, and it's
rather annoying.

-- 
Thomas

             reply	other threads:[~2002-10-05  9:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-05  9:07 Thomas Langås [this message]
2002-10-05 18:11 ` Unable to kill processes in D-state Robert Love
2002-10-05 18:27   ` Jan Hudec
2002-10-05 23:56     ` Thomas Langås
2002-10-06  2:18       ` jw schultz
2002-10-06  2:37         ` Robert Love
2002-10-06  2:49           ` jw schultz
2002-10-06 10:59             ` Thomas Langås
2002-10-06 12:24               ` jw schultz
2002-10-06 14:36                 ` Thomas Langås
2002-10-06 16:42                   ` Jan Hudec
2002-10-06 17:09                     ` Thomas Langås
2002-10-06 17:43                       ` Jan Hudec
2002-10-06 17:43                         ` Jan Hudec
2002-10-07 12:24                       ` Denis Vlasenko
2002-10-16  0:33                         ` Thomas Langås
2002-10-16  0:33                           ` Thomas Langås
2002-10-06 14:30               ` Graham Murray
2002-10-06 14:54                 ` Thomas Langås
2002-10-06 20:26             ` Rik van Riel
  -- strict thread matches above, loose matches on Subject: below --
2002-10-06 19:50 Jeremy Sanders

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021005090705.GA18475@stud.ntnu.no \
    --to=tlan@stud.ntnu.no \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.