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
> > >
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
On Thu, 2007-05-03 at 02:40 -0700, Andrew Morton wrote:
> Monitor the system using the taskstats interface. There is a sample
> application and documentation in Documentation/accounting/.
>
> Your monitoring application will receive a netlink packet each time a process
> exits. It includes the
On Thu, 03 May 2007 06:34:42 +0930 Glen Turner <[EMAIL PROTECTED]> wrote:
> The question is, how can a process with no relationship to another
> process detect that process unexpectedly dying?
Monitor the system using the taskstats interface. There is a sample
application and documentation in
Hi Russell,
Thanks for your answer.
> If you did have a process which polls for the service, what happens if
> that process dies?
The failure mode is good. The monitoring process dies, the
interface stays up, ospfd keeps advertising the route, named
keeps running. We pick up the lack of a
On Thu, May 03, 2007 at 06:34:42AM +0930, Glen Turner wrote:
> 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.
Okay.
> We don't want to poll, because that isn't
On Thu, May 03, 2007 at 06:34:42AM +0930, Glen Turner wrote:
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.
Okay.
We don't want to poll, because that isn't pretty
Hi Russell,
Thanks for your answer.
If you did have a process which polls for the service, what happens if
that process dies?
The failure mode is good. The monitoring process dies, the
interface stays up, ospfd keeps advertising the route, named
keeps running. We pick up the lack of a
On Thu, 03 May 2007 06:34:42 +0930 Glen Turner [EMAIL PROTECTED] wrote:
The question is, how can a process with no relationship to another
process detect that process unexpectedly dying?
Monitor the system using the taskstats interface. There is a sample
application and documentation in
On Thu, 2007-05-03 at 02:40 -0700, Andrew Morton wrote:
Monitor the system using the taskstats interface. There is a sample
application and documentation in Documentation/accounting/.
Your monitoring application will receive a netlink packet each time a process
exits. It includes the exit
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
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
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
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
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
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
16 matches
Mail list logo
