Potential issue with && shell operator and upstart command parsing

Garrett Cooper yanegomi at gmail.com
Mon Oct 27 20:50:54 GMT 2008

On Mon, Oct 27, 2008 at 10:55 AM, Scott James Remnant
<scott at netsplit.com> wrote:
> On Mon, 2008-10-27 at 10:42 -0700, Garrett Cooper wrote:
>> The issue still persists, which makes me thing that upstart is
>> evaluating the test statement as a failure and as such pre-start fails
>> and in the end takes down the rest of the job lifecycle. Is that in
>> fact the case?
> Upstart doesn't evaluate it at all, it just passes the whole thing over
> to /bin/sh
>> [PEXPECT]# initctl start /etc/init/jobs.d/umasktest_doesntwork
>> initctl: Unable to start job: Unknown job: /etc/init/jobs.d/umasktest_doesntwork
> Try without the "/etc/init/job.s.d" on the front?
> Scott
> --
> Have you ever, ever felt like this?
> Had strange things happen?  Are you going round the twist?

Yeah... I was just being a tard --

[PEXPECT]# initctl start umasktest_doesntwork
initctl: Unable to start job: Job failed to start

More information about the upstart-devel mailing list