[Bug 1704677] [NEW] 229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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: systemd (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: regression-proposed xenial
-- 
229-4ubuntu18: '+' command prefix does not work in ExecStart*= and ExecStop*=
https://bugs.launchpad.net/bugs/1704677
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to systemd in Ubuntu.