[13:43] I am working on writing an upstart job for a program that has three daemons that must be started in a specific order, stopping is not so important but the prefer order is the same in reverse. Can this be done with one upstart job or is it needed to write one for each daemon? [15:15] I am working on writing an upstart job for a program that has three daemons that must be started in a specific order, stopping is not so important but the prefer order is the same in reverse. Can this be done with one upstart job or is it needed to write one for each daemon? [15:16] frederickjh: if you want those three daemons monitored by upstart, you need to split them [15:16] ok [15:16] Thats what I thougt. [15:17] I had tried with two as a test in a job but only the second one was running at the end. [15:17] two exec lines? [15:17] yes [15:17] yeah, the parser only takes the last parsed line [15:17] ok [20:42] I have another question regarding the program with three daemons. I think it is possible to have another job with the name of the collective program that could emit a job and start the others. [20:43] But is it possible to check the status of the "dummy" job and have it return the status of the 3 daemons? [20:45] Instead of having to check the status of three daemons individually. [23:42] no [23:43] Is it possible to have an upstart script start and stop based on an old sysv script? [23:50] Seq: no, not really [23:51] afaik, fedora has patched the rc script to emit events when an sysv script is started and stopped [23:53] /etc/rc.d/rc, to be specified [23:53] mbiebl: Thanks. I don't control the other init script, so modifying it would be troublesome. [23:53] that does not help you though, if you e.g. stop a sysv script via /etc/init.d/ stop [23:54] mbiebl: true, I hadn't thought of that.