Am 07.08.20 um 13:10 schrieb Michael Biebl:
> 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
Hi all,
This bug just hit several of my machins and VMs, and nealy destroyed
several of them because I didn't catch the sheer amount of logspam
caused by this in time.
I would strongly advise a bulletin or something is put out, or the change
reverted until a fix is decided upon upstream or in Deb
Hi,
I found this bugreport after already opening one with resolvconf and
I just thought I'd link you to the one I made:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968015
Cheers,
Thomas Mühlbacher
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.
Fwi
Am 06.08.20 um 08:55 schrieb Michael Biebl:
> From what I read at
> https://github.com/systemd/systemd/commit/708961c7011b7578d3e6e10ca463d15edb62b5c1
> (which is the commit responsible for this issue), this change appears to
> be deliberate and maybe resolvconf just needs to add a
> RemainAfterExi
Am 05.08.20 um 14:38 schrieb Kai Lüke:
> Yes, I had resolvconf around for some reason while using systemd-resolved.
Thanks for your additional information. It was very helpful.
From what I read at
https://github.com/systemd/systemd/commit/708961c7011b7578d3e6e10ca463d15edb62b5c1
(which is the com
I too find both installed on all my machines.
What sense does that make?
Shouldn't the packages conflict?
> "KL" == Kai Lüke writes:
KL> Yes, I had resolvconf around for some reason while using systemd-resolved.
KL> Thanks for forwarding to upstream.
Yes, I had resolvconf around for some reason while using systemd-resolved.
Thanks for forwarding to upstream.
Am 04.08.20 um 20:14 schrieb Michael Biebl:
> 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.
>>
>> I checked if the trigger was valid but there were n
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.
>
> I checked if the trigger was valid but there were no write events which
> should cause the trigger:
>
Hi,
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-
11 matches
Mail list logo
