[16:01] <jadams> hey, so I have a problem where a command I start in a subshell in an upstart script won't die on service stop.  Some discussion around the problem is here: https://github.com/ddollar/foreman/issues/97
[16:01] <jadams> essentially, the command I ran after the && in my "su - foo -c "a && b" won't stop
[16:01] <jadams> in that example, stopping the service would kill a but not b
[16:35] <xnox> jadams: correct you should have a second upstart job to run b which is "started on stopped a" (sequential)
[16:35] <xnox> jadams: also see "setuid" and "setgid" stanzas which may possibly replace "su" for you.
[16:53]  * SpamapS wishes we could have setuid per-executable
[16:53] <SpamapS> so that pre-start can be root
[17:05] <jadams> xnox: yeah, so it ultimately seems to come down to this problem: https://gist.github.com/knewter/5671928
[17:06] <jadams> xnox: so ultimately, I'm dealing with a ruby app on a deploy, and so my foo actually modifies the current environment (it's an rvm script runner), so I actually just want to run it before running the second command