[10:47] hi [10:47] i've wrote a upstart job, pretty simple. with 'start on filesystem' and a script block creating some directories [10:48] but it doesn't get started. I already tried to run initctl emit filesystem but this seems not to start it either [10:51] uhm looks like its more or less the same job as the rsyslog job. and that job works (-> it get started when emitting 'filesystem' event) [11:01] looks like I can't start the job manually either.. according to strace it seems like it's stopping right after the first != 0 return code is found [11:23] ok fixed that issue and then fixed another issues and lerned about tasks vs services. now it's a task but another job depending on that task doesn't start [14:41] fish_: http://upstart.ubuntu.com/cookbook/#debugging-a-script-which-appears-to-be-behaving-oddly [14:43] all script sections are run with "/bin/sh -e", which indeed makes the shell exit after the first non-zero return code [15:01] JanC: thanks! === fish is now known as fish_ [16:11] I'm trying to put together an upstart job to run browsermob-proxy but the stop command doesn't seem to work, does anyone have any experience with this?