From: Andrew Morton <akpm@linux-foundation.org>
To: Glen Turner <gdt@gdt.id.au>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Detecting process death for anycast named process monitoring
Date: Thu, 3 May 2007 02:40:48 -0700 [thread overview]
Message-ID: <20070503024048.e7192b3b.akpm@linux-foundation.org> (raw)
In-Reply-To: <4638FCEA.4010806@gdt.id.au>
On Thu, 03 May 2007 06:34:42 +0930 Glen Turner <gdt@gdt.id.au> wrote:
> The question is, how can a process with no relationship to another
> process detect that process unexpectedly dying?
Monitor the system using the taskstats interface. There is a sample
application and documentation in Documentation/accounting/.
Your monitoring application will receive a netlink packet each time a process
exits. It includes the exit code and the process's name.
next prev parent reply other threads:[~2007-05-03 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 21:04 Detecting process death for anycast named process monitoring Glen Turner
2007-05-02 22:30 ` Chris Friesen
2007-05-02 23:12 ` David M. Lloyd
2007-05-04 5:54 ` Russell King
2007-05-03 8:01 ` Russell King
2007-05-03 8:55 ` Glen Turner
2007-05-03 9:40 ` Andrew Morton [this message]
2007-05-03 10:17 ` Glen Turner
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=20070503024048.e7192b3b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gdt@gdt.id.au \
--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