From: Doug McNaught <doug@wireboard.com>
To: psusi@cfl.rr.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [bug report] NFS and uninterruptable wait states
Date: 03 Sep 2001 13:42:59 -0400 [thread overview]
Message-ID: <m3sne4p3vg.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <01090310483100.26387@faldara> <m3zo8cp93a.fsf@belphigor.mcnaught.org> <01090311553201.26387@faldara>
In-Reply-To: Phillip Susi's message of "Mon, 3 Sep 2001 11:55:32 +0000"
Phillip Susi <psusi@cfl.rr.com> writes:
> That's all well and good that the process won't get an error back, but imho,
> a process should *NEVER* be beyond the reach of a SIGKILL. I mean, an
> unkillable process prevents a clean shutdown, doesn't it? ( can't kill the
> process, can't unmount the filesystem ).
D state has always meant unkillable. If you don't like it, you now
know how to change it.
-Doug
--
Free Dmitry Sklyarov!
http://www.freesklyarov.org/
We will return to our regularly scheduled signature shortly.
next prev parent reply other threads:[~2001-09-03 17:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-03 10:48 [bug report] NFS and uninterruptable wait states Phillip Susi
2001-09-03 15:11 ` Peter Wächtler
2001-09-03 15:17 ` Peter Wächtler
2001-09-03 15:50 ` Doug McNaught
2001-09-03 11:55 ` Phillip Susi
2001-09-03 17:42 ` Doug McNaught [this message]
2001-09-03 16:28 ` David Woodhouse
2001-09-03 17:09 ` Peter Wächtler
2001-09-03 17:14 ` David Woodhouse
2001-09-03 17:50 ` Doug McNaught
2001-09-10 13:53 ` Jan Hudec
2001-09-03 22:11 ` Sound Blaster Live - OSS or Not? Thiago Vinhas de Moraes
2001-09-03 22:26 ` Tim Jansen
2001-09-03 22:26 ` Thiago Vinhas de Moraes
2001-09-03 22:51 ` Robert Love
2001-09-04 3:38 ` Garett Spencley
2001-09-03 23:03 ` Joel Jaeggli
2001-09-03 23:35 ` machack
2001-09-04 10:54 ` Daryl F
2001-09-04 12:09 ` rui.p.m.sousa
2001-09-04 17:08 ` Thiago Vinhas de Moraes
2001-09-04 17:36 ` rui.p.m.sousa
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=m3sne4p3vg.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=psusi@cfl.rr.com \
/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.