On Tue, 27 Nov 2012, Michael Lindner <michael(a)tropyx.com> wrote:
There was something recently in the IT news about a
problem with NTP
servers, someone hacked the master server or something like that. NTP
works a bit like DNS, so if the root server has a problem all the others
Thanks for the suggestion, but NTP doesn't work like DNS in that way.
With DNS you have a list of root servers which have the addresses for Top
Level Domain (TLD) servers such as "au" and "com", those servers then
addresses for domains under them.
With NTP you just have an IP address of a server to talk to, you shouldn't
need anything else. If you specify multiple servers then the one which has
the lowest stratum (the lowest number of hops from an atomic clock) will be
I've idly considered hooking up a GPS receiver to my PC and making it a
stratum 1 server.
Not sure if this was your problem, but the solution
was something like
(perhaps) choose a different NTP server and (definitely) restart NTP -
does this help?
Restarting the ntpd made the problem go away. But it would be nice to know
why it happened and how to prevent it from happening in future. It's not fun
to have this problem become noticable when "make" reports timestamp errors
when building things from the NFS server.
Might need to explicitly run it from the command line
once to get it to
sync if it's really out, using a "don't worry what diff" flag setting.
Apologies for the vagueness, bit late for me to look it up properly :-D
ntpdate is the way to directly set it from the command-line. But I prefer to
just start it and let it do it's thing. If the difference is less than 20
minutes then it can manage it by itself.
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/