Re: Extending the update-rc.d API to change runlevel and disable scripts?
sean finney <email@example.com> writes:
> On Friday 25 April 2008 06:24:41 pm Russ Allbery wrote:
>> Yes please. Another desperately needed feature is a query interface
>> that will tell you exactly the current state of a given init script,
>> for use by other automated tools. Currently, Puppet hacks around this
>> in some really ugly ways since there's no good interface for this.
> you mean like invoke-rc.d --query ?
No, that seems to be something completely different.
Puppet needs to know if a given init script is configured to ever start or
whether it's administratively disabled (K scripts at every runlevel), what
runlevels it starts and stops at (more generally), and its priority
(although dependency-based boot should make that unnecessary).
Puppet would also love to be able to disable a script and then put it back
with the same priority that it had before, although dependency-based boot
will make that obsolete soon enough, hopefully.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>