implementing serialized startup sequence

[Janne Karhunen]

On Mon, Mar 15, 2010 at 6:26 PM, Scott James Remnant <scott at netsplit.com> wrote:

>> >> 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?

Well that's the thing - currently you have to choose between
two sub-optimal solutions to create a critical section (start on
started|stopped, possibly binding two unrelated tasks together
or the maintenance command runner).


> 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?

Possibly something along the lines of:

start on something
serial section
  job1
  job2
  job3
end serial section

At least it would not be a script running maintenance stuff, even
though it can be implemented via one.


-- 
// Janne