[systemd-devel] Warning to Distros: NetworkManager + systemd + nscd + nmcli deadlock issue on boot.
gmane at colin.guthr.ie
Mon Apr 2 06:56:26 PDT 2012
'Twas brillig, and Michal Schmidt at 02/04/12 14:47 did gyre and gimble:
> Colin Guthrie wrote:
>> So in this situation, as systemd is aiming for network.target, but
>> it's not actually reached it yet, systemctl condrestart nscd appears to
>> hang, presumably waiting for network.target to be reached (as nscd.service
>> is ordered After network.target).
> Does reverting commit dd17d38 "job: fix loss of ordering with restart jobs" help?
> As noted in the patch description, try-restart needs to be improved to finish
> quickly when the service is not running. I will be looking into this.
As mentioned on IRC, I suspect it will. However, at first glance, I
think the logic itself is fairly sound (blocking to wait for it seems
reasonable in the circumstances) and the --no-block argument should work
around things OK (if it weren't all hardcoded via the legacy initscript
I'll try and get a proper answer for you tonight as to whether it was
that commit that caused this issue to bubble up to the surface.
Tribalogic Limited http://www.tribalogic.net/
Mageia Contributor http://www.mageia.org/
PulseAudio Hacker http://www.pulseaudio.org/
Trac Hacker http://trac.edgewall.org/
More information about the systemd-devel