| 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
| ||
|
Message-ID: <4639111A.70202@nortel.com> Date: Wed, 02 May 2007 16:30:50 -0600 From: "Chris Friesen" <cfriesen@...tel.com> To: Glen Turner <gdt@....id.au> CC: Linux kernel <linux-kernel@...r.kernel.org> Subject: Re: Detecting process death for anycast named process monitoring 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 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. We did something similar where arbitrary processes can register to be sent an arbitrary signal when the state of other processes change. The caller passes in the pid, the signal to be sent, and an event mask describing which events you're interested in (stop/start/exit/kill/etc.). A signal number of 0 means to deregister interest in the specified pid. Chris - 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/
Powered by blists - more mailing lists