Hi Scott and Casey, I was thinking about one feature that's lacking in upstart that's present in sysv init: backwards dependency starting and stopping. Here's an example usecase: - Service A is dependent on Service B. Right now what you have to do is start Service B, and because we don't have a means for profiling jobs, we either would have to have something like:
Service B emits Event B Service A starts on Event B What would be nice is something of the form: Service A is started Service B is started as a requirement of Service A I'm not sure if this may be the mentality that you're looking for with upstart, but it would make the tool a lot easier to use for developers than it currently is. Just my 2 cents... Thanks! -Garrett -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel