Public bug reported:
The systemd version 229-4ubuntu18 from xenial-proposed archive has a
bug. The '+' prefix (see
https://www.freedesktop.org/software/systemd/man/systemd.service.html)
in ExecStart*= and ExecStop*= statements does not work any longer.
File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
this version contains two commands prefixed with '+':
# When resolved is in use, it must be brought up before we consider networking
# available because otherwise there is a window where DNS resolution doesn't
# work.
[Unit]
Before=network-online.target
# tell resolvconf about resolved's builtin DNS server, so that DNS servers
# picked up via networkd are respected when using resolvconf, and that software
# like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
# resolution
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] ||
/sbin/resolvconf -d systemd-resolved'
Those two statements in section [Service] lead to the following two
error messages in dmesg:
[ 3.687475] systemd[1]:
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable
path is not absolute, ignoring: +/bin/sh -c '[ ! -e
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" |
/sbin/resolvconf -a systemd-resolved'
[ 3.687614] systemd[1]:
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable
path is not absolute, ignoring: +/bin/sh -c '[ ! -e
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: regression-proposed xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1704677
Title:
229-4ubuntu18: '+' command prefix does not work in ExecStart*= and
ExecStop*=
Status in linux package in Ubuntu:
Incomplete
Bug description:
The systemd version 229-4ubuntu18 from xenial-proposed archive has a
bug. The '+' prefix (see
https://www.freedesktop.org/software/systemd/man/systemd.service.html)
in ExecStart*= and ExecStop*= statements does not work any longer.
File /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf of
this version contains two commands prefixed with '+':
# When resolved is in use, it must be brought up before we consider networking
# available because otherwise there is a window where DNS resolution doesn't
# work.
[Unit]
Before=network-online.target
# tell resolvconf about resolved's builtin DNS server, so that DNS servers
# picked up via networkd are respected when using resolvconf, and that
software
# like Chrome that does not do NSS (libnss-resolve) still gets proper DNS
# resolution
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] || echo
"nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
ExecStopPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] ||
/sbin/resolvconf -d systemd-resolved'
Those two statements in section [Service] lead to the following two
error messages in dmesg:
[ 3.687475] systemd[1]:
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:12] Executable
path is not absolute, ignoring: +/bin/sh -c '[ ! -e
/run/resolvconf/enable-updates ] || echo "nameserver 127.0.0.53" |
/sbin/resolvconf -a systemd-resolved'
[ 3.687614] systemd[1]:
[/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf:13] Executable
path is not absolute, ignoring: +/bin/sh -c '[ ! -e
/run/resolvconf/enable-updates ] || /sbin/resolvconf -d systemd-resolved'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704677/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
