Not necessarily. I have seen some systems that have a poor clock that just can't keep the clock in sync with NTP. I have one laptop and a server in particular (both are Dells, hmmm) that within a week get several minutes out of sync. I have other systems configured identically that keep perfect time. On those two systems I have cron periodically stop NTP, run ntpdate against an NTP server, then restart NTP.
I use to run something called Chrony intead of NTP on the laptop and it was able to keep the clock in sync.
Thomas Zehetbauer wrote:
Obviously the NTP server you configured cannot be reached.
Find a list of mostly public NTP stratum 1 and 2 servers here: http://www.eecis.udel.edu/~mills/ntp/clock1b.html http://www.eecis.udel.edu/~mills/ntp/clock2b.html
I recommend you to use 3 stratum 2 servers.
Tom
-- Greg Gulik http://www.gulik.org/greg/ greg @ gulik.org
