[systemd-devel] Antw: Re: Does "systemctl daemon-reload" discard service information?

Ulrich Windl Ulrich.Windl at rz.uni-regensburg.de
Tue May 21 07:50:47 UTC 2019

>>> Andrei Borzenkov <arvidjaar at gmail.com> schrieb am 20.05.2019 um 19:07 in
Nachricht <4d103eef-d000-c9b2-9f7a-e0cda8ed625b at gmail.com>:
> 20.05.2019 16:36, Ulrich Windl пишет:
>> Hi!
>> I have had the effect that a "systectl status" before and after a
>> "daemon-reload" is different, while the service in question wasn't 
> restarted:
> ...>
>> Is that intentional?
> daemon-reload is known to lose state for years. Some problems get fixed,
> new problems appear. Problems range from cosmetic to losing state of
> units and jobs causing callers of systemd to "hang" waiting for job
> completion. Unfortunately daemon-reload is often the only answer to
> other reported problems (like in "systemd does not see fstab changes?
> Run daemon-reload, where is the problem").

So it's a bug?

> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org 
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel 

More information about the systemd-devel mailing list