On 31/10/13 13:06, Thorsten Glaser wrote:
>> My understanding is that something like `update-rc.d $service disable`
>
> … isn’t that overwritten by the update-rc.d commands in the
> maintainer scripts (postinst) when the package is upgraded?
Not in the sysv-rc implementation, at least. `update-rc.d $service
disable` does not remove the symlinks: instead, it renames the S??
symlinks to K??, so the service is stopped in all runlevel changes.
sysv-rc interprets this as "installed, but disabled by the sysadmin".
For the defaults (and deprecated start/stop) actions, "If any files
named /etc/rc${runlevel}.d/[SK]??${name} already exist then update-rc.d
does nothing", according to the man page, so maintainer scripts that do
"the obvious thing" shouldn't accidentally re-enable daemons.
In the past, some packages' maintainer scripts might have incorrectly
re-enabled daemons as a side-effect of adjusting the boot sequence order
(e.g. moving a daemon's start links from S20foo to S30foo), but AIUI
that was always considered to be a bug, and now that we have insserv,
it's a piece of error-prone maintainer script that isn't needed any more.
S
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52725ded.5080...@debian.org
