Bug#967906: systemd 246 resolvconf path unit
biebl at debian.org
Mon Aug 17 09:27:30 BST 2020
Am 07.08.20 um 13:10 schrieb Michael Biebl:
> 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
> in resolvconf-pull-resolved.path
Checking the archive, potentially affected packages are:
-> triggers the start of cups.service, a potentially long running
service, so most likely not affected
-> Type=oneshot service using RemainAfterExit=yes, so seemingly not affected
-> starts systemd-ask-password-plymouth.service, Type=simple with
ExecStart=/usr/bin/systemd-tty-ask-password-agent --watch --plymouth
The "--watch" argument means, it's continuously running and processing
password requests, so should be safe
-> starts resolvconf-pull-resolved.service, Type=oneshot without
So in this list the only affected service that seems to be affected.
I was considering cloning/reassigning this bug report to resolvconf, but
there is already https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968015
I think it makes sense to bump the severity of #968015 to at least
important or even RC, as it is hitting its users hard.
Given that only resolvconf is affected, I don't think it is necessary to
back out this changed behaviour of PathExits= (which now behaves as
documented) in systemd.
I do think though, that rate limiting should be applied and I'll keep
this systemd bug report to track this progress.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the Pkg-systemd-maintainers