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
signature.asc
Description: OpenPGP digital signature
