I like to call em dead processes.. other like to call em disk processes
meaning they're in the middle of interrupted i/o.. it's normal for
processes to be in the D state for a few milliseconds or so... but after
everything else has settled.. you have a problem. Only solution is to
reboot. I had a major problem with one of the 2.4.0-test kernels and
deadlocked processes. Any reproducable problem should be reported to the
project maintainter ASAP.. and in this case.. it's a kernel issue.. but
can be caused by "3rd party" patches, etc.
On Wed, 21 Mar 2001, Prashant Ramachandra wrote:
> On Tuesday, March 20, 2001 5:38 PM, WANG Meng [SMTP:[EMAIL PROTECTED]] wrote:
> |
> | Does anybody know how to stop a process with flag "D"?
>
> It's dead. You can't stop that.
>
> --
> Prashant TR <[EMAIL PROTECTED]> | Web: http://www.midpec.com/
>
> Ignore other people's ignorance so that you may discover your own wisdom
> - Anonymous
>
>
>
>----------------------------------------------------------------------------------------------------------------------------
> The information transmitted is intended only for the person or entity to which it is
>addressed and may contain confidential
> and/or privileged material. Any review, retransmission, dissemination or other use
>of, or taking of any action in reliance upon,
> this information by persons or entities other than the intended recipient is
>prohibited. If you received this in error, please
> contact the sender and delete the material from any computer.
>
>----------------------------------------------------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
>
--
-Statux
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
