Message-Id: <200505041708.j44H80lR016289@turing-police.cc.vt.edu>
To: Deepak <deepakgaur@fastmail.fm>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hanged/Hunged process in Linux 
In-Reply-To: Your message of "Wed, 04 May 2005 14:38:48 +0900."
             <1115185128.12535.233322099@webmail.messagingengine.com> 
From: Valdis.Kletnieks@vt.edu
References: <1115185128.12535.233322099@webmail.messagingengine.com>
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="==_Exmh_1115226479_4721P";
	 micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Date: Wed, 04 May 2005 13:08:00 -0400
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1511
Lines: 40

--==_Exmh_1115226479_4721P
Content-Type: text/plain; charset=us-ascii

On Wed, 04 May 2005 14:38:48 +0900, Deepak said:
> I am working on a Linux based system and developing a monitoring process
> which shall do the following function

> Anybody having another definition for a "Hanged process" in Linux
> context

Around here, the big issue is usually a process stuck in 'D' state - in
other words, a process that's done a syscall or otherwise entered the
kernel (page faults and AIO being other possibilities) and hasn't returned.
Since signals are delivered at return time, even a 'kill -9' wont do the
desired thing.  These are almost always the result of either kernel bugs
or hardware failures.

There was a lengthy thread a while ago about how to deal with these, and the
consensus was that there's *NO* good general way to un-wedge such a process,
and that fixing the underlying bug or hardware fault is the only way to deal
with it.

--==_Exmh_1115226479_4721P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFCeQFvcC3lWbTT17ARAmGUAKDxLax6U1n+ENwKZKYS6/TPoFdRhgCg3q6z
ia04Qu/3ql9mTzQXnnceqrE=
=8pEM
-----END PGP SIGNATURE-----

--==_Exmh_1115226479_4721P--
-
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/