Your message dated Sat, 21 Jul 2018 00:48:47 +0200
with message-id <[email protected]>
and subject line Re: Bug#806812: Double messages upon disable
has caused the Debian Bug report #806812,
regarding remove the first systemctl SysV service script synchronizing warning,
only leave the second
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
806812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806812
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-3
File: /bin/systemctl
Do you see how users might be alarmed if they see:
# systemctl enable mysql
Synchronizing state of mysql.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mysql
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
# systemctl enable mysql
Synchronizing state of mysql.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable mysql
And thus need to execute the command the second time just to make sure?
Going the other way makes
# systemctl disable mysql
Synchronizing state of mysql.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable mysql
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
# systemctl disable mysql
Synchronizing state of mysql.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable mysql
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
# systemctl disable mysql
Synchronizing state of mysql.service with SysV service script with
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install disable mysql
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
Apparently there is a 'before' inspection and warning, then the command
is executed, and then there is an 'after' inspection and warning. (Each
single warning I am talking about consists of two lines.)
So you need to eliminate the 'before' inspection and warning, or at
least the 'before' warning.
Or, at least write the steps as they probably really occur:
# systemctl disable mysql
Synchronizing state of mysql.service with SysV service script with
/lib/systemd/systemd-sysv-install.
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
Executing: /lib/systemd/systemd-sysv-install disable mysql
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
--- End Message ---
--- Begin Message ---
On Fri, 29 Jan 2016 00:54:34 +0100 Michael Biebl <[email protected]> wrote:
> Am 29.01.2016 um 00:31 schrieb Michael Biebl:
>
> > 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?
>
> On second thought, it's probably cleaner, if we change update-rc.d
> directly to not output this information, so the tool behaves consistently.
I guess if this would ever be fixed, it should be in insserv, where this
message should be downgraded to a debug message.
That said, update-rc.d no longer strictly depends on insserv to create
/etc/rc?.d/ symlinks. Insserv is no longer installed by default which is
why I consider this issue sufficiently addressed and I'm going to close
this bug report against systemd.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
