On 5/4/05, Deepak <[email protected]> wrote:
> (1) A process not accepting any signals and consuming system resources
wrong. It may have decided to go through a critical section of its job, and
the job takes a long time.
> (2) A process in STOP state
wrong. The prosess is being debugged or is stopped (killall -STOP bash).
Besides, often the RUNNING state is more suspicious.
> (3) A process in deadlock state
how can you detect this from outside of the process(es)?!
> Process conforming to definition 3 will be due to race conditions/bad
> programming.Definition 1 does define a proper hanged process but is it
> possible to create such a process in LInux as in linux signal delivery
> to the process and its handling is assured by the Linux kernel.
Anything, except for SIGKILL and SIGSTOP can be overridden.
And it doesn't help you anyway in detecting of runaway processes.
> Anybody having another definition for a "Hanged process" in Linux
> context
Except for the case described by Valdis Klietnieks, it's hard to define.
How do you distinguish between a very busy process and the deadly
locked in itself one?
You'll probably end up defining some arbitrary timeouts for the
processes under your control, some watchdog interface for the
processes and plain old kill(..., SIGCONT); kill(..., SIGKILL); restart();
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
