Stefano Zacchiroli wrote:
On Fri, Apr 25, 2008 at 10:15:27AM +0200, Petter Reinholdtsen wrote:
Similarly, a counter action for this new disable action should be
provided. I frequently dig into postinsts to retrieve the info about in
which position I should put back a service I've disabled.
[Luk Claes]
Isn't this just a matter of stopping the service and renaming the S (K)
links to s (k) links so one can easily revert?
Probably not. When only stop symlinks are present, one need to know
which runlevels should keep the stop symlinks, and which should be
changed. I suspect the
On Sun, Apr 27, 2008 at 09:41:49AM +0200, Petter Reinholdtsen wrote:
[Luk Claes]
Isn't this just a matter of stopping the service and renaming the S (K)
links to s (k) links so one can easily revert?
Probably not. When only stop symlinks are present, one need to know
which runlevels
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
sean finney [EMAIL PROTECTED] 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
On Fri, Apr 25, 2008 at 10:15:27AM +0200, Petter Reinholdtsen wrote:
I believe we should extend the update-rc.d interface to provide a few
more operations that are commonly needed and commonly done wrong.
Neat, thanks for the initiative.
Disable scripts
---
This has to be done
Petter Reinholdtsen [EMAIL PROTECTED] writes:
I believe we should extend the update-rc.d interface to provide a few
more operations that are commonly needed and commonly done wrong.
- One operation to modify the runlevel used by a script/service.
- One operation to disable a script and
7 matches
Mail list logo
