[05:35] how do i turn off an upstart job from starting automatically? [05:36] http://upstart.ubuntu.com/cookbook/#disabling-a-job-from-automatically-starting [08:31] Hey I was a question I was hoping someone might know the answer to [08:32] are you able to put multiple exec's in say a pre-start script block? [08:34] thatguydan: "exec" overlays the running program in the current process with the new program, so no. [08:35] thatguydan: that's just shell/unix behaviour. What are you trying to do? [08:35] chown a few items in a pre-start script, but it wasn't executing :s [08:35] thatguydan: just run your chowns without the exec. [08:36] yup, just tried and worked. Not sure why I was adamant on the exec's, new to upstart [08:36] thanks [08:38] thatguydan: the exec's your talking about are actually shell keywords. Take a look at http://askubuntu.com/questions/162768/starting-java-processes-with-upstart and have a poke around in the Cookbook (http://upstart.ubuntu.com/cookbook/). [08:38] cheers, will do [08:39] thatguydan: it's worth remembering that Upstart will run all shell code using /bin/sh so it's worth re-reading "man sh" too (see also http://upstart.ubuntu.com/cookbook/#develop-scripts-using-bin-sh and http://upstart.ubuntu.com/cookbook/#debugging-a-script-which-appears-to-be-behaving-oddly and http://upstart.ubuntu.com/cookbook/#check-a-script-section-for-errors). [08:40] will do [08:41] I have one more quick question, using the task stanza, if I exec a .sh script, it shouldn't restart it on exit 1, but will on exit 0, is that correct? [08:44] We're trying to write some update scripts on hardware, and I was thinking of putting a script in that checks for a flag file to decide whether to update or not