Ntpdate not updating clock online dating in seattle
The ntp daemon won't adjust the local time if the offset is too great.
That's why a lot of ntpd startup scripts use ntpdate to sync the clock before startings ntpd.
What happens when you run ntpdate and then startup ntpd?
Here is the Ubuntu 10.0.4 in its entirety, with comments removed: 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 ntp.restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery restrict 127.0.0.1 restrict ::1 I welcome feedback on how this config might be improved. I can sync time of win7 from a ntp linux server manually. When "down to the millisecond" matters, however, I found that Windows wouldn't actually make the adjustment; as if "oh, I'm off by 2.5 seconds, close enough bro, nothing to see or do here".I also made a ticket with my VPS provider asking them for a detailed recommendation on the best thing to do.I pointed them to this thread, and some other documentation indicating that maybe the CPU allocation would cause a timing problem.