[Pkg-sysvinit-devel] Bug#560222: insserv: How to disable a service permanently?
Andreas Berger
andreas.berger.01 at gmail.com
Sat Apr 14 05:32:37 UTC 2012
On Saturday, April 14, 2012 01:14:03 you wrote:
> Hi Andreas
>
> > the bug still exists in stable (version 1.14.0-2) and from what i
> > remember also in testing.
> >
> > steps to reproduce:
> >
> > 1) insserv -r service
> > 2) aptitude full-upgrade
> > result: service is running again if the service was in the upgrade
> >
> >
> > may i propose this be more than wishlist:
> >
> > for one, the expected behavior is that package upgrades do not override
> > user- made system configurations without asking (this is the case at
> > least when dealing with config files from what i've seen). disabling a
> > service with insserv is, from a user view, just as much part of a system
> > configuration as editing some .conf file, hence should be respected just
> > as much.
>
> insserv is the wrong interface to disable services. insserv -r *removes*
> links to services and that's exactly what it does, it does not disable the
> links from ever returning and never will be extended to do that.
>
> Update-rc.d has an interface for disabling initscript execution, though
> arguably this interface should be in the service(8) command. This was
> mentioned earlier in the bug report.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560222#10
>
> Thanks, Kel
i see,
i was under the wrong impression that insserv and update-rc.d did the same
thing, and that using update-rc.d was deprecated. so 'insserv -r' is like
'update-rc.d remove', but what i really should do is 'update-rc.d disable',
which creates 'stop' links rather than deleting 'start' links.
thanks,
andreas
More information about the Pkg-sysvinit-devel
mailing list