[08:12] <warly> Hello, what is the equivalent of doing sh -x /etc/init.d/<script> with upstart?
[14:46] <ion> warly: Add to the beginning of the script section of interest:
[14:46] <ion> exec >/path/to/log 2>&1
[14:46] <ion> set -x
[14:47] <warly> ion: thanks
[14:48] <ion> ellyjones: The environment variables listed in stopped(7) should be available in the post-stop script.
[14:48] <ion> ellyjones: RESULT is probably what you’re after.
[14:48] <ellyjones> ion: thanks :)
[14:49] <Stevee> hello, is anything known about the development process or a possible release date of the next upstart version ?
[14:50] <ion> It’s Being Developed™ and the release date is When It’s Done™. :-P
[14:51] <Stevee> wow, that are really great news ....
[14:52] <ion> ellyjones: Scratch that, they in fact aren’t. Let’s see...
[14:53] <Stevee> upstart is a great tool a great project, but i hate this kind of closed development process ...
[14:53] <ellyjones> (I ended up wrapping the job in a script instead)
[14:56] <ion> ellyjones: What will definitely work is another job that has ‘task’, ‘start on stopped foo’, ‘script … (do something with "$RESULT") … end script’. Perhaps Keybuk knows how to do that without an auxiliary job.
[14:58] <ellyjones> I phrased it as: if ! $CMD; then $CLEANUP; fi and just made it a script
[14:59] <ion> stevee: Many of us agree. Keybuk is the one to talk about that.
[15:27] <Stevee> never mind, thanks ion