Please do this only if you trust everybody on the network! Here i am using Raspian_For_Banana Pi_v3.1 on a Banana Pi.
#disable auth #broadcastclient , monitoring the network traffic and more carefully reading the fine print of NTPd docs, I realized that NTPd requires unrestricted access to UDP port 123 for both outgoing and incoming traffic. The reason for the -7294 sec offset was that the /etc/init.d/ntp script was starting the /var/lib/ntp/dhcp as the config file for ntpd (-c), this file was using 192.168.0.1 as timerserver.
Well, some of these questions (your bullet list including "why 5 servers") are a little difficult to answer, time synchronization is quite the rabbit hole.
The old parable about the man with one clock knowing what time it is but the man with two never being sure...
Several work-arounds offered with at least: * compile your own version of ntp or restore from pre-mavericks * force touching of the drift file so that pacemaker re-reads it I haven't tried any yet.
I am running raspbian wheezy, upgraded to all the latest packages.
#statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day enable # You do need to talk to an NTP server or two (or three).
I talked to one of their senior tech support staff.
It seems like the only real fix is to replace Apple's broken ntpd and configuration.
For a thorough explanation, see this guy's post: This thread looked like a good explanation of the issue and the possible work-around. start=45&tstart=0#27183298 Basically pacemaker conflicts with Apple modified ntp on Mavericks.
restrict 127.0.0.1 #restrict ::1 # Clients from this (example!
) subnet have unlimited access, but only if # cryptographically authenticated.