Re: administration of initscripts
On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote:
> > I have been using Debian for many years now. In all of that time I
> > have never wanted to "manage" init scripts. I always wonder. What
> > are people trying to do?
> > What is more complicated than this. If you want it then install it.
> > If you don't want it then remove or purge it. With those two commands
> > all management is handled automatically.
> I don't know need/use multiple run-levels. But I do wish it were
> easier/standard to disable particular services. Uninstalling the
> corresponding package is not always an option (e.g. I'm thinking of the
> network-manager package, for example, or a daemon which you prefer to
> run "on demand" when a particular user logs in, ...).
update-rc.d foo disable|enable
is one method.
> Many daemons can be disabled via their /etc/default/foo file, but not
> all and not always in the same way (e.g. for one of them I had to
> put an "exit 1" in that file since there was no var for it).
Enabling/disabling via /etc/default is very bad practice. That's
circumventing the init system. For one thing, the service dependency
graph won't be adjusted for services which appear "enabled" but are in
fact disabled in the /etc/default file--this status is "hidden" from
insserv, and could result in boot failure since we think things are
OK when they are in fact not. Dependent services are going to break,
Getting rid of all the /etc/default disable options will be a release
goal for jessie.
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800