Bug#806812: Double messages upon disable

[Michael Biebl]

Control: tag -1 = confirmed

On Tue, 05 Jan 2016 07:20:41 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson
<jidanni at jidanni.org> wrote:
> After an install or an enable, the next disable will be good, but a
> second and subsequent disable will have the repeated lines.
> 
> # systemctl disable haveged
> Synchronizing state of haveged.service with SysV init with /lib/systemd/systemd-sysv-install...
> Executing /lib/systemd/systemd-sysv-install disable haveged
> insserv: warning: current start runlevel(s) (empty) of script `haveged' overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `haveged' overrides LSB defaults (0 1 6).
> # systemctl disable haveged
> Synchronizing state of haveged.service with SysV init with /lib/systemd/systemd-sysv-install...
> Executing /lib/systemd/systemd-sysv-install disable haveged
> insserv: warning: current start runlevel(s) (empty) of script `haveged' overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `haveged' overrides LSB defaults (0 1 6).
> insserv: warning: current start runlevel(s) (empty) of script `haveged' overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `haveged' overrides LSB defaults (0 1 6).

I can confirm the issue. Putting a set -x at the top of
/lib/systemd/systemd-sysv-install reveals the following:

> + getopt -o r: --long root: -- disable haveged
> + eval set --  -- 'disable' 'haveged'
> + set -- -- disable haveged
> + true
> + shift
> + break
> + [ -n  ]
> + NAME=haveged
> + [ -n haveged ]
> + /usr/sbin/update-rc.d haveged defaults
> insserv: warning: current start runlevel(s) (empty) of script `haveged' overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `haveged' overrides LSB defaults (0 1 6).
> + /usr/sbin/update-rc.d haveged disable
> insserv: warning: current start runlevel(s) (empty) of script `haveged' overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `haveged' overrides LSB defaults (0 1 6).

So, update-rc.d <foo> defaults complains when it's being run for a
disabled service, and update-rc.d <foo> disable complains if you run it
for an already disabled service.

The first time you run systemctl disable <foo>, it will only show the
error message from update-rc.d <foo> disable.


Fwiw, I don't find those warnings particularly helpful. They look more
like debug messages to me. Maybe we could hide any output from
update-rc.d if the return code == 0.

Martin et all, thoughts?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20160129/0a66c10c/attachment.sig>