On Mon, Oct 27, 2008 at 10:55 AM, Scott James Remnant <[EMAIL PROTECTED]> 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 >From /var/log/messages: Oct 27 20:43:59 10 <1225140239,500361>init: umasktest_doesntwork goal changed from stop to start Oct 27 20:43:59 10 <1225140239,500713>init: umasktest_doesntwork state changed from waiting to starting Oct 27 20:43:59 10 <1225140239,502055>init: Handling starting event Oct 27 20:43:59 10 <1225140239,502692>init: umasktest_doesntwork state changed from starting to pre-start Oct 27 20:43:59 10 <1225140239,554004>init: umasktest_doesntwork pre-start process (813) Oct 27 20:43:59 10 <1225140239,809150>init: umasktest_doesntwork pre-start process (813) terminated with status 1 Oct 27 20:43:59 10 <1225140239,812454>init: umasktest_doesntwork goal changed from start to stop Oct 27 20:43:59 10 <1225140239,812887>init: umasktest_doesntwork state changed from pre-start to stopping Oct 27 20:43:59 10 <1225140239,813954>init: Handling stopping event Oct 27 20:43:59 10 <1225140239,814655>init: umasktest_doesntwork state changed from stopping to killed Oct 27 20:43:59 10 <1225140239,814870>init: umasktest_doesntwork state changed from killed to post-stop Oct 27 20:43:59 10 <1225140239,815082>init: umasktest_doesntwork state changed from post-stop to waiting Oct 27 20:43:59 10 <1225140239,838302>init: Handling stopped event Strangely enough when I change it to `console owner', it works: Oct 27 20:47:24 10 <1225140444,364006>init: Handling starting event Oct 27 20:47:24 10 <1225140444,366345>init: umasktest_doesntwork state changed from starting to pre-start Oct 27 20:47:24 10 <1225140444,410167>init: umasktest_doesntwork pre-start process (827) Oct 27 20:47:24 10 <1225140444,583342>init: umasktest_doesntwork pre-start process (827) exited normally Oct 27 20:47:24 10 <1225140444,583993>init: umasktest_doesntwork state changed from pre-start to spawned Oct 27 20:47:24 10 <1225140444,625965>init: umasktest_doesntwork main process (830) Oct 27 20:47:24 10 <1225140444,636831>init: umasktest_doesntwork state changed from spawned to post-start Oct 27 20:47:24 10 <1225140444,638757>init: umasktest_doesntwork state changed from post-start to running Oct 27 20:47:24 10 <1225140444,655660>init: Handling started event Oct 27 20:47:24 10 <1225140444,671961>init: umasktest_doesntwork main process (830) exited normally Oct 27 20:47:24 10 <1225140444,674011>init: umasktest_doesntwork goal changed from start to stop Oct 27 20:47:24 10 <1225140444,675203>init: umasktest_doesntwork state changed from running to stopping Oct 27 20:47:24 10 <1225140444,677718>init: Handling stopping event Oct 27 20:47:24 10 <1225140444,679601>init: umasktest_doesntwork state changed from stopping to killed Oct 27 20:47:24 10 <1225140444,680909>init: umasktest_doesntwork state changed from killed to post-stop Oct 27 20:47:24 10 <1225140444,682149>init: umasktest_doesntwork state changed from post-stop to waiting Oct 27 20:47:24 10 <1225140444,689996>init: Handling stopped event -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
