[10:27] <owend> Hello world.  I asked my question of cjwatson but he sent me here, so I'll try here...
[10:27] <owend> Is there a way of finding out which events of an Upstart job's start on A and B clause the job has yet received?
[13:49] <jodh> owend: The easiest thing to do is just enable verbose logging (http://upstart.ubuntu.com/cookbook/#obtaining-a-list-of-events) before the job starts. If that's not possible, there is a more precise way of establishing which events a job has already received, but note that this latter method isn't via a command - you can infact inspect upstarts inner state (assuming upstart 1.6.1+).
[22:00] <cschneid> I have an upstart job that seems to track the pid correctly, but hangs when I do `service myjob start` and `service myjob stop` even though if I ctrl-c it has the right pid during a status call
[22:02] <cschneid> This is the script & the behavior I'm seeing. https://gist.github.com/cschneid/4fb0757f7e71bf7cb745
[23:23] <postmodern> what is the correct way to set a custom PATH for an upstart script?