Andrei Borzenkov writes:
systemd waits for all processes to stop. ntpd starts at least one more process for asynchronous resolver. It's possible that this process may get blocked and ignores SIGTERM. It is even possible that it gets blocked somewhere in a library call and so the reason is outside of ntpd.
OK, I didn't think about the DNS resolver. That might be another push to make the switch to NTPsec on this machine also.
I am not sure how to debug it, given that it seems to happen on shutdown only (and logs presented here are obviously from system shutdown as well). I thought that it may be related to network being stopped too early, but simple minded "systemctl stop network; systemctl stop ntpd" still has no delay.
Well, I could actually reproduce it by shutting down ntpd via systemctl.
But if someone can reproduce it with high probability (I cannot) running with systemd debug level output is the first step.
After yesterday's kernel update the shutdown was without any delay. I actually rebooted and did another (immediate) shutdown and that went OK also. If it's still reproduceable, I'll follow up with your suggestion about the systemd debugging.
systemd does exactly the same in both cases - it either runs ExecStop or sends signal, so I do not see how it is going to change anything.
OK. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org