On Fri, 2010-04-09 at 13:39 +0000, Bernd Zeimetz wrote:
> > Upstart runs all shell scripts with "set -e" by default.
>
> So what if the script is *not* run by upstart, but by somebody trying to figure out why things work (or not)?
> If you need to assume that a piece of shell code is executed with -e being set, add a set -e before that piece of code. Don't assume it will be called with sh -e...
>
The syntax of these files is such that they can only be run by Upstart,
unless you copy & paste the shell fragment out and run it directly --
but then you're missing a lot of the set-up that Upstart does for you.
So that's really not recommended ;-)
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
On Fri, 2010-04-09 at 13:39 +0000, Bernd Zeimetz wrote:
> > Upstart runs all shell scripts with "set -e" by default.
>
> So what if the script is *not* run by upstart, but by somebody trying to figure out why things work (or not)?
> If you need to assume that a piece of shell code is executed with -e being set, add a set -e before that piece of code. Don't assume it will be called with sh -e...
>
The syntax of these files is such that they can only be run by Upstart,
unless you copy & paste the shell fragment out and run it directly --
but then you're missing a lot of the set-up that Upstart does for you.
So that's really not recommended ;-)
Scott
--
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?