initctl event chain to start on correspondence question (was "Re: umask 7000 invalid with upstart (!)?")

[Sandeep Puddupakkam (spuddupa)]

Garrett,
The "start on" condition of emit_ooh should be modified as

start on multiple=1 event=2 are=3 fine=3 too=4
ie start on <event> <environment variables without and/or>
here multiple=1 is the event and event,are,fine,too are treated as environment variables.
The emits stanza you have in the job emit_blah is informational only.

Sandeep

-----Original Message-----
From: upstart-devel-bounces at lists.ubuntu.com [mailto:upstart-devel-bounces at lists.ubuntu.com] On Behalf Of Garrett Cooper
Sent: Tuesday, September 08, 2009 3:43 PM
To: Upstart Dev List
Subject: initctl event chain to start on correspondence question (was "Re: umask 7000 invalid with upstart (!)?")

On Tue, Sep 8, 2009 at 3:41 PM, Garrett Cooper<yanegomi at gmail.com> wrote:
> Hi,
>    Really basic question. If I do something like the following:
>
>    initctl emit multiple=1 events=2 are=3 fine=4 too=5
>
>    This should result in the event chain:
>
>    multiple=1 and events=2 and are=3 and fine=4 and too=5
>
>    correct? I ask because when I try and do the following, it fails:
>
> [nova-cavium17:~]$ cat /etc/init/jobs.d/emit_blah
> emits multiple events are fine too
> exec initctl emit multiple=1 events=2 are=3 fine=4 too=5
> [nova-cavium17:~]$ cat /etc/init/jobs.d/emit_ooh
> start on multiple=1 and events=2 and are=3 and fine=4 and too=5
> [nova-cavium17:~]$ start emit_blah
> [nova-cavium17:~]$ status emit_ooh
> emit_ooh not running
>
>    Is this expected to work or am I missing some subtle note somewhere..?
> Thanks,
> -Garrett

Ugh... forgot to rename the subject. Sorry ><.
-Garrett

-- 
upstart-devel mailing list
upstart-devel at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel