Bug#967906: systemd 246 resolvconf path unit

Kai Lüke kailueke at riseup.net
Tue Aug 4 18:14:48 BST 2020


in my case this was caused by the resolvconf-pull-resolved.path unit
which continuously triggered the resolvconf-pull-resolved.service unit.

I checked if the trigger was valid but there were no write events which
should cause the trigger:

  inotifywait -m -e modify /run/systemd/resolve/stub-resolv.conf
  Setting up watches.
  Watches established.
  # no further output

Starting the service unit actually works but because it starts so often,
it hits the restart burst limit and is reported as failed (but still
will be started immediately again).

A workaround was to remove the resolvconf package which was not really
needed in my case anyway, I guess.

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


More information about the Pkg-systemd-maintainers mailing list