[13:50] <Takumo> Hi all, if I have two jobs, A and B, and job B needs job A to work
[13:51] <Takumo> can job A do "emit a-running" and B have "start on a-running" ?
[13:55] <jodh> Takumo: yes, but you don't need to do that: just make B specify "start on started A". See http://upstart.ubuntu.com/cookbook/#event and http://upstart.ubuntu.com/cookbook/#start-depends-on-another-service.
[13:58] <jodh> Takumo: note that if you really want A to emit your custom 'a-running' event, it should call 'initctl emit a-running' but also specify 'emits a-running' for 'initctl check-config' (see http://upstart.ubuntu.com/cookbook/#initctl-check-config).
[14:06] <Takumo> oh ok, so just leave A without any emits and have b do "start on started A"
[14:07] <Takumo> awesome :)
[14:07] <jodh> Takumo: correct :) Upstart provides a set of standard events for jobs (starting/started/stopping/stopped). They all have man pages too.
[14:09] <Takumo> that's nice
[16:19] <Psi-Jack> I'm trying to create an upstart job that loads a non-forking, non-daemonizing PHP script which keeps itself running in the foreground. But, when I do so, it just starts it, and stops immediately with an exit code of 1, and debugging it, I can't seem to find any further details why it's just not working.
[16:23] <jodh> Psi-Jack: this is all covered in the cookbook: http://upstart.ubuntu.com/cookbook/#determining-why-your-service-fails-to-start, http://upstart.ubuntu.com/cookbook/#checking-how-a-service-might-react-when-run-as-a-job
[16:23] <jodh> , http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in
[16:23] <jodh>  
[16:23] <Psi-Jack> I kinda figured out what it was. sudo errored about not having a tty.
[22:35] <leomurilloz> anybody know how I can execute an action on job respawn?