Bug#967906: systemd 246 resolvconf path unit

Michael Biebl biebl at debian.org
Fri Aug 7 12:10:47 BST 2020


Am 04.08.20 um 19:14 schrieb Kai L√ľke:
> Hi,
> 
> in my case this was caused by the resolvconf-pull-resolved.path unit
> which continuously triggered the resolvconf-pull-resolved.service unit.

...

> Would be good to see if the PathChanges is broken in general and then
> report this upstream.

Fwiw, it is not PathChanged= which triggers this issue but PathExists=,
which now behaves like originally documented.

To workaround the issue, you can comment out the line

PathExists=/run/systemd/resolve/stub-resolv.conf
in resolvconf-pull-resolved.path

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200807/ae7747ab/attachment.sig>


More information about the Pkg-systemd-maintainers mailing list