Ability to kill (was: Re: so, no way to kill process? have to reboot?)

From: vda (vda@port.imtp.ilyichevsk.odessa.ua)
Date: Fri Oct 12 2001 - 05:06:22 EST

PW> Well, I'd suspect it in "D" state - waiting for some disk I/O to
PW> finish...

If a process is stuck in D state it's a kernel bug - I
don't think it's ever legitimate to wait forever for something
which could never happen. However, some such bugs are rarely
happening (e.g. a swapin failure due to hdd malfunction)
and thus will unlikely be fixed.

PW> But in "R" with your described behavior looks like a bug.
PW> If you care about the CPU time waisted: what about kill -STOP <pid>?

R state unkillable hang is possible too (infinite loop in kernel
preventing return from a syscall).

In short, in my understanding any syscall should return sooner
or later in order to process to be killable. Anything preventing
that is a kernel bug.

However, I'm not a UNIX guru, I may be wrong.
I really like to be enlightened if I'm wrong.

Best regards, vda

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Mon Oct 15 2001 - 21:00:44 EST