From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Hanged/Hunged process in Linux
Date: Wed, 4 May 2005 09:09:53 -0700 [thread overview]
Message-ID: <20050504090953.20b57374@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <1115185128.12535.233322099@webmail.messagingengine.com>
On Wed, 04 May 2005 14:38:48 +0900
"Deepak" <deepakgaur@fastmail.fm> wrote:
> I am working on a Linux based system and developing a monitoring process
> which shall do the following function
>
> (1) It will detect abnormally terminated application process and will
> restart the process group
>
> (2) It will detect a hanged application and will restart it
>
> My query is regarding second point . What should be the proper
> definition of a "Hanged Process" in Linux context . I searched on google
> regarding it and got the following definitions
>
> (1) A process not accepting any signals and consuming system resources
> (2) A process in STOP state
> (3) A process in deadlock state
>
> 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.
>
> Anybody having another definition for a "Hanged process" in Linux
> context
>
> Deepak Gaur
It is impossible to absolutely tell the difference between a very busy process and one
that is hung. Better to build to build hang detection into the process itself with
a heartbeat interface. Look at the hangcheck timer, nmi_watchdog, and watchdog
devices.
--
Stephen Hemminger <shemminger@osdl.org>
next prev parent reply other threads:[~2005-05-04 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 5:38 Deepak
2005-05-04 16:09 ` Stephen Hemminger [this message]
2005-05-04 17:08 ` Valdis.Kletnieks
2005-05-04 20:51 ` Alex Riesen
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=20050504090953.20b57374@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®