Exactly, Upstart works with everybody's children.<div><br><div class="gmail_quote">On Fri, Dec 10, 2010 at 12:54 AM, Yang Zhang <span dir="ltr"><<a href="mailto:yanghatespam@gmail.com">yanghatespam@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Ah - FWIW, supervisord also relies on SIGCHLD, it just works with its<br> own children.<br> <div><div></div><div class="h5"><br> On Thu, Dec 9, 2010 at 4:49 PM, Scott James Remnant <<a href="mailto:scott@netsplit.com">scott@netsplit.com</a>> wrote:<br> > Nothing to do with trace, it's to do with actually getting the SIGCHLDs back<br> > when the processes die.<br> > On Fri, Dec 10, 2010 at 12:45 AM, Yang Zhang <<a href="mailto:yanghatespam@gmail.com">yanghatespam@gmail.com</a>> wrote:<br> >><br> >> On Thu, Dec 9, 2010 at 4:36 PM, Scott James Remnant <<a href="mailto:scott@netsplit.com">scott@netsplit.com</a>><br> >> wrote:<br> >> > you can't run your "own" upstart since it relies<br> >> > on being PID 1 to do process supervision<br> >><br> >> I believe you but I'm curious - do you mean upstart needs ptrace<br> >> priveleges, specifically? What, besides fork, does it trace?<br> ><br> ><br> <br> <br> <br> </div></div>--<br> <div><div></div><div class="h5">Yang Zhang<br> <a href="http://yz.mit.edu/" target="_blank">http://yz.mit.edu/</a><br> </div></div></blockquote></div><br></div>