On 2014-01-18 10:58, Achim Gratz wrote:
Carlos E. R. writes:
But once systemd tells ntpd to start, if it takes long it does not have to do with systemd at all.
The relation to systemd is probably (I can't test this anymore) that the old init system started xdm before firing off ntp. Systemd does it the other way around, thus annoyingly exposing the delay.
I don't know if I can still test this. I have old virtual machines, but they never use ntpd. However, xdm is precisely one of the services that can cough if time jumps backwards, so it does no sense to start xdm in advance.
Typical delay cause would be no network, or configured peers not responding fast.
As I said before, the wait is ultimately caused by still unexplained disk activity and more specifically uncached metadata. Warming the cache by restarting ntp once is also slow, but subsequent restarts of ntp take almost no time.
But this makes no sense; ntp is not a huge program such that loading it from disk would be that slow. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)