Heh funny you should ask that one, but I just added the code to my local branch to do that for 0.6 - you can't run your "own" upstart since it relies on being PID 1 to do process supervision, but you'll be able to have your own jobs, events, etc.<div> <br></div><div>Scott<br><div><br><div class="gmail_quote">On Fri, Dec 10, 2010 at 12:32 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;"> I seem to remember being told by upstart folks that work is under way<br> to allow non-root users to configure their own jobs for upstart (not<br> just start/stop jobs). Is there an ETA on this?<br> <br> Alternatively (or better yet), can users run their own upstarts/inits?<br> This seems to be a more general solution.<br> <br> Currently, we're using a mix of supervisord and our own control<br> scripts that capture some of upstart's dependency/event infrastructure<br> (which supervisord lacks).<br> --<br> Yang Zhang<br> <a href="http://yz.mit.edu/" target="_blank">http://yz.mit.edu/</a><br> <font color="#888888"><br> --<br> upstart-devel mailing list<br> <a href="mailto:upstart-devel@lists.ubuntu.com">upstart-devel@lists.ubuntu.com</a><br> Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/upstart-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/upstart-devel</a><br> </font></blockquote></div><br></div></div>