[systemd-devel] timesyncd: Frequent polling when no server could be reached

[Florian Lindner]

Hello,

I tried out timesyncd today. Basically worked out of the box (disabled ntpd, 
enabling systemd-timesyncd and systemd-networkd, both unconfigured, side by 
side with NetworkManager).

At my universities network they are blocking outgoing UDP why I can't reach 
any NTP timesyncd gives these message every 10 seconds:

Aug 21 09:45:00 asaru systemd-timesyncd[317]: Timed out waiting for reply 
from 216.239.32.15:123 (time1.google.com).
Aug 21 09:45:00 asaru systemd-timesyncd[317]: Using NTP server 
[2001:4860:4802:32::f]:123 (time1.google.com).
Aug 21 09:45:00 asaru systemd-timesyncd[317]: Using NTP server 
216.239.34.15:123 (time2.google.com).
Aug 21 09:45:10 asaru systemd-timesyncd[317]: Timed out waiting for reply 
from 216.239.34.15:123 (time2.google.com).
Aug 21 09:45:10 asaru systemd-timesyncd[317]: Using NTP server 
[2001:4860:4802:34::f]:123 (time2.google.com).
Aug 21 09:45:10 asaru systemd-timesyncd[317]: Using NTP server 
216.239.36.15:123 (time3.google.com).

Polluting my log this way. Is is possible to inhibit that behavior? Maybe 
trying a couple of times, then giving up until next network status change.

Another question I have is about the NTP status output of timedatectl.

Right now (with ntpd running) it says:

NTP enabled: yes
NTP synchronized: no
 
I suppose it need some more uptime than the 11 minutes I have currently?

When I had timesyncd active it said NTP no, though I had a ntp client 
runnung, albeit definitly unsynchronized.

Version is 215

Thanks,
Florian