System clock not updating
For users who do not want to enable location services, in situations where the Mac is not accessing the internet, or for whatever reason just don’t want to use the recommended automatic time detection settings (maybe you’re building a time machine?
How exciting), you can also manually set the clock and date and time yourself in Mac OS X.
driftfile /var/lib/ntp/ntp.drift 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 server 0.server 1.server 2.server 3.I know NTP doesn't necessarily bring the clock in time immediately. For example, remote refid st t when poll reach delay offset jitter ============================================================================== ns1.1.23 2 u 10 64 1 1.043 0.258 0.001 ns2.62.1 2 u 9 64 1 0.671 0.135 0.001 ns3.62.1 2 u 8 64 1 0.750 0.277 0.001 (We also switched to servers recommenced by the hosting company, but that is beside the point.) The commands in brent's answer were helpful because they made me realise the problem was in network access to the NTP servers, not in NTP configuration itself. The ntpdate command returns something like "17 Dec ntpdate: no server suitable for synchronization found".
Still, how many hours or days you need to wait in order to reasonably expect that NTP has done its job and synced the clock? Is there any quick way to check if configuration is correct and whether the chosen NTP servers return the correct time? However, on other machines the same command gives something meaningful!
Download and install Adobe Reader and restart your computer once again.
Am I missing some other configuration file or option, or just doing something wrong? Edit: output of remote refid st t when poll reach delay offset jitter ============================================================================== ns1.nexellent.n . I'm starting to suspect that some firewall settings for this particular server cause the problem...
So we asked the server hosting provider to allow NTP for our machines, and now it works fine.
I'll accept this for now, because most likely the problem is related to those. If I had to guess as to why and assuming you have network connectivity and can see your NTP Host without a problem then it could be you have drifted to a large value.
If the time difference is greater than X (Sorry I dont remember what X is offhand) than a warning will be printed and time will not be syncd.