Bug#975591: insserv: warns too loudly when local admin disables a script ( …overrides LSB =?UTF-8?Q?defaults=E2=80=A6?=)

Thorsten Glaser tg at mirbsd.de
Mon Nov 23 21:15:30 GMT 2020


Package: insserv
Version: 1.21.0-1
Severity: wishlist
X-Debbugs-Cc: tg at mirbsd.de, pkg-systemd-maintainers at lists.alioth.debian.org

Cc’ing init-system-helpers maintainer address, as
parts of this probably affect it as well.

From a discussion on debian-init-diversity, using…

	sudo /usr/sbin/update-rc.d -f $initscriptname disable

… is the “correct” way for the local administrator
to disable the init script. This, however, causes
loud warnings not only running that command, but
during package upgrades as well:

insserv: warning: current start runlevel(s) (empty) of script `rng-tools-debian' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `rng-tools-debian' overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `rng-tools-debian' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `rng-tools-debian' overrides LSB defaults (0 1 6).

First, this warning is shown twice each, which is
probably a (cosmetic) bug.

Second, this warning shouldn’t be shown if a local
administrator has (deliberately) disabled a script.

If you think that, as Lorenzo said, it’s important
telling the admin that their local setup differs
from maintainer defaults, then please special-case
the “admin specifically disabled the script manually”
case from others, and issue a message e.g. like:

insserv: reminder: the script “rng-tools-debian” was disabled by the local administrator.

(And also please do *not* use the grave accent ‘`’
for anything. That’s typographically just wrong.)

If at all. Other tools don’t periodically warn if
the local administrator changes a configuration
file.



If, however, update-rc.d disable is _not_ the current
“proper” way of disabling an init script locally, then
please document which it is. People recently adviced
using update-rc.d remove instead, which doesn’t survive
package upgrades and therefore isn’t stable enough.
(Probably best to document these in the update-rc.d(8)
manpage anyway, and which survive package upgrades.)


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-updates'), (500, 'buildd-unstable'), (500, 'unstable'), (500, 'oldstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-3-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages insserv depends on:
ii  libc6  2.31-4

insserv recommends no packages.

Versions of packages insserv suggests:
pn  bootchart2  <none>

-- no debconf information


More information about the Pkg-systemd-maintainers mailing list