Package: systemd
Version: 235-2
Severity: normal
Something about the service configuration for systemd-resolved doesn't
match what the service manager expects. What does it mean to start an
executable path with "!!" ?
0 dkg@alice:~$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-resolved.service.d
└─resolvconf.conf
Active: inactive (dead)
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Tasks: 0 (limit: 4915)
CGroup: /system.slice/systemd-resolved.service
Oct 16 16:16:23 alice systemd[1]:
/lib/systemd/system/systemd-resolved.service:22: Executable path is not
absolute: !!/lib/systemd/systemd-resolved
Oct 16 16:16:23 alice systemd[1]:
/lib/systemd/system/systemd-resolved.service:22: Executable path is not
absolute: !!/lib/systemd/systemd-resolved
Oct 16 16:16:24 alice systemd[1]:
/lib/systemd/system/systemd-resolved.service:22: Executable path is not
absolute: !!/lib/systemd/systemd-resolved
3 dkg@alice:~$ systemctl cat systemd-resolved | grep ExecStart
ExecStart=!!/lib/systemd/systemd-resolved
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
0 dkg@alice:~$
-- Package-specific info:
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'),
(200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (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.116
ii libacl1 2.2.52-3+b1
ii libapparmor1 2.11.0-11
ii libaudit1 1:2.7.8-1
ii libblkid1 2.30.2-0.1
ii libc6 2.24-17
ii libcap2 1:2.25-1.1
ii libcryptsetup4 2:1.7.5-1
ii libgcrypt20 1.7.9-1
ii libgpg-error0 1.27-3
ii libidn11 1.33-2
ii libip4tc0 1.6.1-2
ii libkmod2 24-1
ii liblz4-1 0.0~r131-2+b1
ii liblzma5 5.2.2-1.3
ii libmount1 2.30.2-0.1
ii libpam0g 1.1.8-3.6
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.7-2
ii libsystemd0 235-2
ii mount 2.30.2-0.1
ii procps 2:3.3.12-3
ii util-linux 2.30.2-0.1
Versions of packages systemd recommends:
ii dbus 1.11.20-1
ii libpam-systemd 235-2
Versions of packages systemd suggests:
ii policykit-1 0.105-18
ii systemd-container 235-2
Versions of packages systemd is related to:
ii dracut 045+132-1
pn initramfs-tools <none>
ii udev 235-2
-- no debconf information
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
