Re: Detecting process death for anycast named process monitoring

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...

- DML

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

Relevant Pages

  • Re: Detecting process death for anycast named process monitoring
    ... process detect that process unexpectedly dying? ... we want to shut down the interface ... which causes Quagga to inject the anycast route. ...
    (Linux-Kernel)
  • Re: Multicast problems
    ... The new code phases out the hack which this define refers to, which is to encode 24 bits of an interface index in 0.0.0.0/8. ... I didn't roll a patch for Quagga as it's not part of the base system. ... It is probably easier for the purposes of Quagga to use the Linux-derived ip_mreqn extension to the IP_MULTICAST_IF ioctl for interface selection, as ospf should be using a locally-scoped address -- although the MCAST_JOIN_GROUP ioctl is the one to use if one needs to bind to an interface by index and be sure that it actually worked. ...
    (freebsd-current)
  • possible (kernel) bug with zebra
    ... with gre and tuninterfaces and quagga. ... Panics occurs sometimes ... Then it downs the interface. ... >routes are not correct. ...
    (freebsd-stable)
  • Re: Sharing a COM object in a MMF
    ... I'm not sure the DirectX interfaces will work cross-process -- there's a lot ... > property that returned the D3D Device interface. ... >> I am trying to inject a D3D device into a existing process and then give ...
    (microsoft.public.win32.programmer.directx.graphics)
  • Re: Sharing a COM object in a MMF
    ... I'm not sure the DirectX interfaces will work cross-process -- there's a lot ... > property that returned the D3D Device interface. ... >> I am trying to inject a D3D device into a existing process and then give ...
    (microsoft.public.win32.programmer.kernel)