On Thu, May 22, 2014 at 01:48:23PM +0300, Eliezer Croitoru wrote: > Well manually using a crontab with ntpdate to a pool of servers should be > good enough right?
Not really. NTPdate steps the clock forward or backwards instantaneously. Depending on how bad your system clock is, that could be a jump of several seconds. Now, which came first? This midnight or that midnight? NTPd, on the other hand, delicately adjusts the clock frequency so that the clock drifts back into synchronisation. So your seconds might be 0.01% shorter than real, but they still all happen in the right sequence. ntpdate is really only any good being run once (at boot), for example if you have a clock that can't keep time while the system is off. > > Eliezer > > On 05/22/2014 07:09 AM, Murray Trainer wrote: > >Hi Eliezer, > > > >We had the same errors a few weeks ago. Turned out the time on our NFS > >server was out by over 30 secs as NTP wasn't setup correctly . Looks like > >the time on one of yours is out by about 250 secs (361-105). > > > >Murray
signature.asc
Description: Digital signature
