linux-kernel - Re: Detecting process death for anycast named process monitoring

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070504055425.GA24362@flint.arm.linux.org.uk>
Date:	Fri, 4 May 2007 06:54:26 +0100
From:	Russell King <rmk+lkml@....linux.org.uk>
To:	"David M. Lloyd" <dmlloyd@...rg.com>
Cc:	Chris Friesen <cfriesen@...tel.com>, Glen Turner <gdt@....id.au>,
	Linux kernel <linux-kernel@...r.kernel.org>
Subject: Re: Detecting process death for anycast named process monitoring

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:
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/