On Mon, 14 Mar 2011 10:58:19 -0600 Thomas S Hatch <thatch45@xxxxxxxxx> wrote: > But regardless, this should support the Arch style runlevel. maybe... in theory it's possible that in a month we switch to systemd as official init system. this will probably not happen (soon), but just saying. > I do think that if it is possible to determine the ordering based on > the requires statements of other services that would be great the key thing imho is that currently on a normal, single Arch install it's the admin who configures the ordering, very explicitly. Automatically guessing an implicit ordering based on whatever heuristics is not how Arch currently does it, and probably neither should puppet. I don't have any puppet experience, but is it not possible to just make the admin configure the order in puppet? Or even just define $DAEMONS in puppet? It's remarkable that such a simple configuration syntax in rc.conf (an ordered list of daemons) is causing these issues, it seems as if puppet tries to abstract (too much?) and now we must work around the limitations of that abstraction? BTW: I was right across Nigel at the devops dinner in Brussels. small world :) Dieter
