From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "David M. Lloyd" <dmlloyd@flurg.com>
Cc: Chris Friesen <cfriesen@nortel.com>, Glen Turner <gdt@gdt.id.au>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Detecting process death for anycast named process monitoring
Date: Fri, 4 May 2007 06:54:26 +0100 [thread overview]
Message-ID: <20070504055425.GA24362@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1178147547.26507.96.camel@localhost>
On Wed, May 02, 2007 at 06:12:27PM -0500, David M. Lloyd wrote:
> On Wed, 2007-05-02 at 16:30 -0600, Chris Friesen wrote:
> > Glen Turner wrote:
> >
> > > The question is, how can a process with no relationship to another
> > > process detect that process unexpectedly dying? If named goes
> > > away to a better place, we want to shut down the interface
> > > which causes Quagga to inject the anycast route.
>
> > We did something similar where arbitrary processes can register to be
> > sent an arbitrary signal when the state of other processes change.
>
> What about something like inotify, but for processes? That would be
> cool...
Or maybe just ignoring the SIGHUP before exec'ing the named process as
a child.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-05-04 5:54 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 [this message]
2007-05-03 8:01 ` Russell King
2007-05-03 8:55 ` Glen Turner
2007-05-03 9:40 ` Andrew Morton
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=20070504055425.GA24362@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=cfriesen@nortel.com \
--cc=dmlloyd@flurg.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.