On Sat, 11 Feb 2017 17:17:20 +0100 Martin Pitt wrote:
No, I did test it with our current systemd package and it worked. However, I
apparently only tested it with resolvconf installed, but not without
resolvconf. Trivial fix, pushed:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/comm
Am 11.02.2017 um 17:17 schrieb Martin Pitt:
> Michael Biebl [2017-02-10 19:20 +0100]:
>> I guess this should only be used in addition with ProtectSystem=, which
>> is a recent upstream change but the Debian version does not use that yet.
>
> No, I did test it with our current systemd package and i
On Fri, 10 Feb 2017 18:29:05 +0100 Goran LAZAREVIC
wrote:
> Same bug here, temporary workaroud is to edit :
> /usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
> and quote as following :
>
> [Service]
> ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] ||
> echo "
Control: tag -1 pending
Michael Biebl [2017-02-10 19:20 +0100]:
> Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> >
> > With the update to 232-17, systemd-resolved fails to start with the
> > following error:
> >
>
> > -- The error number returned by this process is 2.
> > Feb 10 17:46:31 test sy
Control: severity -1 important
Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
>
> With the update to 232-17, systemd-resolved fails to start with the
> following error:
>
> -- The error number returned by this process is 2.
> Feb 10 17:46:31 test systemd[1]: systemd-resolved.service: Main process
Am 10.02.2017 um 17:49 schrieb Yuri D'Elia:
> Package: systemd
> Version: 232-17
> Severity: normal
>
> With the update to 232-17, systemd-resolved fails to start with the
> following error:
>
> -- The error number returned by this process is 2.
> Feb 10 17:46:31 test systemd[1]: systemd-resolved
Same bug here, temporary workaroud is to edit :
/usr/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf
and quote as following :
[Service]
ExecStartPost=+/bin/sh -c '[ ! -e /run/resolvconf/enable-updates ] ||
echo "nameserver 127.0.0.53" | /sbin/resolvconf -a systemd-resolved'
#ReadWrit
Package: systemd
Version: 232-17
Severity: normal
With the update to 232-17, systemd-resolved fails to start with the following
error:
Feb 10 17:46:31 test systemd[1]: Starting Network Name Resolution...
-- Subject: Unit systemd-resolved.service has begun start-up
-- Defined-By: systemd
-- Supp
8 matches
Mail list logo