[18:25] <thewoolleyman> anyone home?
[18:46] <thewoolleyman> how can I tell upstart to call a stop script which is different than a start script?  e.g. start is /bin/start-myservice and stop is /bin/stop-myservice?
[18:48] <ion> pre-stop exec /bin/stop-myservice. But make sure Upstart actually tracks the process started by start-myservice. The easiest way is to make it not daemonize.
[18:49] <thewoolleyman> ion: if I make it not daemonize upstart will keep track of the process?
[18:49] <ion> Yes. And if you add a respawn stanza, Upstart will also restart it if it dies.
[18:57] <thewoolleyman> ion: the docs are extremely unhelpful on that.
[18:58] <thewoolleyman> ion: so what does the stop action do by default?
[18:59] <thewoolleyman> ion: how does it know what to stop and how?
[19:02] <ion> It runs the pre-stop command, if any, then sends SIGTERM to the main pid, then sends SIGKILL if it’s still running after a timeout and finally runs the post-stop command, if any.
[19:02] <ion> The main pid being the one “status jobname” prints.
[19:06] <thewoolleyman> ion: ok, thanks.  the docs don't make that clear at all.  where should I submit a doc bug/patch?
[19:06] <ion> https://launchpad.net/upstart
[19:16] <thewoolleyman> ion: thanks a lot for your help.