Potential issue with && shell operator and upstart command parsing
Scott James Remnant
scott at netsplit.com
Mon Oct 27 17:55:35 GMT 2008
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
> [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?
Have you ever, ever felt like this?
Had strange things happen? Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20081027/35339f51/attachment.pgp
More information about the upstart-devel