[14:12] <djh> Hi. I have a process that gets started by a shell script, which I've been told to move to being controlled by upstart. This naturally runs into problems with the PID that upstart gets when running the script isn't the PID of the daemon that gets started. I tried using "expect daemon" but this lea to suffering from the bug reported at https://bugs.launchpad.net/upstart/+bug/406397 where the process became unkillable.
[14:12] <djh> Is there a "good" way to have Upstart manage an application that needs to be started & stopped by a shell script?
[14:14] <ion> How about making it not daemonize?
[14:14] <ion> No need to use “expect” then.
[14:15] <ion> If you prevent Upstart from tracking the process it won’t know if it crashes.
[14:15] <djh> How do I stop it daemonizing?
[14:16] <ion> Depends on what the script is and does.
[14:18] <djh> the script basically does a bunch of environment setup & then calls the server application
[14:20] <SpamapS> djh: many server applications will have an argument to run in the foreground
[14:21] <SpamapS> djh: there's only a few reasons to move server apps into upstart jobs. Either you need to orchestrate it starting up based on hardware/other services.. or you desire basic respawning
[19:14]  * SpamapS carpet bombs http://stackoverflow.com/questions/tagged/upstart with answers...
[19:20] <xaka> ...one of the daemons forks 4 times... - *facepalm*