> -----Original Message-----
> From: Spitzer, Andy (BL60:9D30)
> Sent: Thursday, November 13, 2008 9:35 AM
> To: Beeton, Carolyn (CAR:9D60); [EMAIL PROTECTED]
> Subject: Re: [sipX-dev] consequences of supervisor crash
>
> Woof!
>
>
> On Thu, 13 Nov 2008 08:36:32 -0500, Carolyn Beeton
> <[EMAIL PROTECTED]> wrote:
>
> > The main consequence of a crash in the supervisor is that
> the child
> > processes are stranded with no parent and no way of
> shutting them down.
> >
>
> One way to prevent this is have the "child" processes detect
> that STDIN closed, and when that happens they commit suicide.
> As stdin is inherited from the parent as a pipe, it closes
> when the parent process closes it (which it would never do,
> normally), or when the parent dies. Orphans cause nothing
> but trouble in our society, and would be best served to kill
> themselves! (What a great quote to get me in trouble when
> taken out of context!)
>
>
> --Woof!
>
This sounds like a good idea too. Without the supervisor, no
xmlrpc-based communication will work, so having the processes continue
to limp along is probably not good. Better to shut down altogether;
someone is bound to notice that!
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
