[RFC] allow specifying startup event

Scott James Remnant scott at netsplit.com
Fri Jan 14 17:53:53 UTC 2011


On Fri, Jan 14, 2011 at 5:48 PM, Serge E. Hallyn
<serge.hallyn at canonical.com> wrote:
> Quoting Scott James Remnant (scott at netsplit.com):
>> There should be no need to alter the existing code to do what you
>> want, and changing things like the startup event means that any job
>> specifying:
>>
>>     start on startup and...
>>
>> would now no longer work!
>
> The lxc.conf which starts on lxc emits startup after doing some
> pre-config, so these should keep working.  (And my laptop with
> these patches has been booting fine)
>
What kind of things do you do here?

(Johan's proposal was that if startup was replaced by a system event,
you could do "starting system" instead of "started system")

> when upstart was started as:
>
>        10991 execve("/sbin/init", ["/sbin/init", "container=lxc", "builtinfstab=/lib/init/fstab.lxc"], [/* 27 vars */] <unfinished ...>
>
This isn't how the kernel starts init when it has these kinds of
things on its command-line, it places container=lxc and
builtinfstab=/lib/init/fstab.lxc into init's *environment* not
arguments.

Scott



More information about the upstart-devel mailing list