implementing serialized startup sequence

[Scott James Remnant]

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

> >> > You could have a job that started things in order:
> >> >
> >> >        start on startup
> >> >        script
> >> >            start job1
> >> >            start job2
> >> >            start job3
> >> >        end script
> >>
> >> That's an option, but it implies a runner task.
> >>
> > What kind of thing were you thinking instead?
> 
> It would be cleaner if init just ran these in defined order
> without actual (manual, scripted) runner. 'Manual' startup
> makes anything possible, of course. I'm not saying it
> makes that big of a difference in real life, I just don't
> happen to like solutions that utilize user maintenance
> commands for normal startup flow.
> 
How would this differ from "start on stopped foo" in each of the jobs?

I'm not really sure I'm understanding what you're after, maybe you could
give me an example what you think the conf files should look like?

Scott
-- 
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 : https://lists.ubuntu.com/archives/upstart-devel/attachments/20100315/2e4f9fbf/attachment.pgp