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