Bug#967906: systemd 246 resolvconf path unit
biebl at debian.org
Fri Aug 7 12:10:47 BST 2020
Am 04.08.20 um 19:14 schrieb Kai Lüke:
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers