Woof! On Tue, 30 Sep 2008 12:53:31 -0400, Scott Lawrence <[EMAIL PROTECTED]> wrote:
> The sipXsupervisor needs to get the status of running the configtest as > a child process. Perhaps a simple pipe() between the two processes as a means of sending back status. Let configtest write the status to stdout, and sipXsupervisor can read it. > Surely we can find a way to put the correct default signal handling in > sipXcommserverLib somewhere (SipXecsService?). Well, I recently changed the signal handling model, and at that time while each "signal thread" was similar to the others, none of them were identical. I didn't see a good way to abstract that all out, or I would have done so at the time. Doesn't mean it cannot be done. I'm just pointing out the amount of effort involved spans more than just sipXsupervisor. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
