[12:37] <munkeh> Am I allowed to ask about upstart v1.5 considering the topic is v1.11?
[12:38] <munkeh> also: Hello
[12:45] <xnox> just ask...
[12:46] <xnox> support for any upstart is provided
[13:11] <munkeh> How do you get a job to start when another job has been respawned?
[13:16] <munkeh> I need to ensure that quagga is only running when unbound is running, and for unbound to respawn on crash.
[13:16] <munkeh> Currently unbound respawns, but quagga does not start again once unbound has respawned.
[13:39] <xnox> munkeh: what are the "stop on" conditions of "unbound"? 
[13:40] <xnox> munkeh: i mean start/stop on conditions of quagga.
[13:43] <munkeh> quagga.conf:  start on unbound started
[13:44] <munkeh> quagga.conf:    stop on unbound stopping
[13:49] <xnox> munkeh: right, i think that would be sufficient. can you try something quite weird:
[13:49] <munkeh> yes.
[13:51] <xnox> munkeh: wait those are wrong. "start on started unbound" and "stop on stopping unbound" is the right way around, no? (or was that the syntax in 1.5?)
[13:51] <xnox> as in the event is "started" and "stopping" with qualifiers of job name "unbound"
[13:51] <xnox> also you can try:
[13:51] <xnox> start on started unbound
[13:51] <xnox> stop on (starting unbound or stopping unbound)
[13:52] <xnox> such that any running instances of quagga are stopped / killed upon a fresh launch of unbound.
[13:54] <munkeh> hang on. I've just done a status quagga and it is still running. quagga is an abstact job to start ospfd. ospfd is stopped, but it's start on starting quagga
[13:54] <munkeh> New meds on my part mean my mind is partially fried.
[14:05] <munkeh> I'll get back to you/this channel once I have it all clear in my head. Thank you for responding. I apologise for being ill-defined.
[14:06] <xnox> munkeh: =))) no worries. all is good. I hope you figure it all out.