Your message dated Sun, 10 Mar 2019 12:08:40 +0100
with message-id <[email protected]>
and subject line Re: systemctl disable --now fails for aliased D-Bus services
has caused the Debian Bug report #804438,
regarding systemctl disable --now fails for aliased D-Bus services
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.)


-- 
804438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804438
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 227-2
Severity: normal

systemctl disable --now foo.service is supposed to stop and disable a
service (there is also an equivalent enable --now command).
I just tried that with firewalld and got:

# systemctl disable --now firewalld
Synchronizing state of firewalld.service with SysV init with 
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install disable firewalld
insserv: warning: current start runlevel(s) (empty) of script `firewalld' 
overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script 
`firewalld' overrides LSB defaults (0 1 6).
Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
Failed to stop dbus-org.fedoraproject.FirewallD1.service: Unit 
dbus-org.fedoraproject.FirewallD1.service not loaded.


The firewalld service is not stopped as a result

firewalld.service has

[Install]
WantedBy=basic.target
Alias=dbus-org.fedoraproject.FirewallD1.service

systemd/systemctl seems to stop the service via the aliased name and we
remove the symlink beforehand. Seems to me, that systemctl should
actually try to stop firewalld.service, and not
dbus-org.fedoraproject.FirewallD1.service.

I haven't checked yet if this is an downstream bug (due to our
systemd-sysv-install script) or something which needs to be fixed
upstream.

So I'm filing this against our bug tracker for now.

We should probably add an autopkgtest for that :-)




-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.113+nmu3
ii  libacl1         2.2.52-2
ii  libapparmor1    2.10-2+b1
ii  libaudit1       1:2.4.4-4
ii  libblkid1       2.27.1-1
ii  libc6           2.19-22
ii  libcap2         1:2.24-12
ii  libcap2-bin     1:2.24-12
ii  libcryptsetup4  2:1.6.6-5
ii  libgcrypt20     1.6.4-3
ii  libkmod2        21-1
ii  liblzma5        5.1.1alpha+20120614-2.1
ii  libmount1       2.27.1-1
ii  libpam0g        1.1.8-3.1
ii  libseccomp2     2.2.3-2
ii  libselinux1     2.3-2+b1
ii  libsystemd0     227-3~test0
ii  mount           2.27.1-1
ii  sysv-rc         2.88dsf-59.2
ii  util-linux      2.27.1-1

Versions of packages systemd recommends:
ii  dbus            1.10.2-1
ii  libpam-systemd  227-3~test0

Versions of packages systemd suggests:
ii  systemd-container  227-3~test0
ii  systemd-ui         3-4

Versions of packages systemd is related to:
ii  udev  227-3~test0

-- no debconf information

--- End Message ---
--- Begin Message ---
On Sun, 08 Nov 2015 15:11:58 +0100 Michael Biebl <[email protected]> wrote:
> Package: systemd
> Version: 227-2
> Severity: normal
> 
> systemctl disable --now foo.service is supposed to stop and disable a
> service (there is also an equivalent enable --now command).
> I just tried that with firewalld and got:
> 
> # systemctl disable --now firewalld
> Synchronizing state of firewalld.service with SysV init with 
> /lib/systemd/systemd-sysv-install...
> Executing /lib/systemd/systemd-sysv-install disable firewalld
> insserv: warning: current start runlevel(s) (empty) of script `firewalld' 
> overrides LSB defaults (2 3 4 5).
> insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script 
> `firewalld' overrides LSB defaults (0 1 6).
> Removed symlink /etc/systemd/system/dbus-org.fedoraproject.FirewallD1.service.
> Failed to stop dbus-org.fedoraproject.FirewallD1.service: Unit 
> dbus-org.fedoraproject.FirewallD1.service not loaded.
> 
> 
> The firewalld service is not stopped as a result
> 
> firewalld.service has
> 
> [Install]
> WantedBy=basic.target
> Alias=dbus-org.fedoraproject.FirewallD1.service


systemctl disable --now firewalld
works as expected now

Running
systemctl disable --now dbus-org.fedoraproject.FirewallD1.service
does not. But the latter is rather a corner case. So while I updated the
upstream bug report, I think closing the downstream bug report is now ok.

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

Attachment: 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

Reply via email to