implementing serialized startup sequence

Scott James Remnant scott at
Mon Mar 15 14:03:58 GMT 2010

On Mon, 2010-03-15 at 15:16 +0200, Janne Karhunen wrote:

> Implementing 'as fast as possible' bootup often requires implementing
> serialized startup sequence(s) we call critical sections.
Do you have any examples of this kind of thing?

We didn't find that we needed any such critical sections for the Ubuntu
boot sequence.

> Any ideas what would be the best way to do these upstart wise? Serializing startup
> based on 'start on started' will surely do it, but that implies a direct
> dependency between tasks A and B and that's not nice. Any other
> options?
You could have a job that started things in order:

	start on startup
	    start job1
	    start job2
	    start job3
	end script

If job1, job2 & job3 have "task" in them - this will run each one in
turn and wait for each one to finish before running the next.

> Stanza support for this would be *extremely* good thing; it would be
> great if we could define the critical sections (say in upstart.conf) one
> way or the other. Scott, any plans for this? We're happy to cook up
> a experimental patch if you consider this worthwhile. We surely do.
How would this differ from the example above?

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
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : 

More information about the upstart-devel mailing list