public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Glen Turner <gdt@gdt.id.au>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Detecting process death for anycast named process monitoring
Date: Thu, 03 May 2007 06:34:42 +0930	[thread overview]
Message-ID: <4638FCEA.4010806@gdt.id.au> (raw)


Hi folks,

Anycast services are a nice way of robustly offering DNS and other
services.  We create an interface which reflects the availability
of the service and advertise that into the network using a OSPF
router like Quagga.

For more detail see
http://www.aarnet.edu.au/~gdt/presentations/2006-07-18-linuxsa-anycast/
which is a summary of work which was presented at linux.conf.au.

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 don't want to be the parent of the running process, because that
doesn't add robustness. If the parent process dies, then the service
dies, and the interface still stays up.

We don't want to poll, because that isn't pretty and the polling
interval needs to be very short on a big ISP's DNS servers.

I have tried using the various notify functions against /proc, but
they don't work for that filesystem. I have tried using notify
against a UNIX domain socket, but notify doesn't work for
that either.

Suggestions, or a patch to support notify for /proc or to push
process death notifications into DBUS or whatever, are welcome.

Thank you, Glen

             reply	other threads:[~2007-05-02 22:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-02 21:04 Glen Turner [this message]
2007-05-02 22:30 ` Detecting process death for anycast named process monitoring 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
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=4638FCEA.4010806@gdt.id.au \
    --to=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