Peter B Van Campen wrote:
Hi,
I have used NTP in previous SUSE 9.X, but on 9.3 I used YAST to set up NTP. YASTs dialog says that it will sync to a time server at bootup. In the past I am sure that the local PC was re-sync'd quite often. I rarely ever saw a difference of more than a second between my "Atomic" wall clock or watch.
But now I see the PCs time getting more and more 'off' the longer it has been booted. This is irritating and non-intuitive. The systems should stay in sync with the 'official' time servers. One should NOT have to re-boot just to get the clock back in sync.
Is the a way to tell the system to regularly 'sync up'? Has anyone out there found a way to keep a 9.3 system time accurate?
PeterB
Is your system running as guest on a VMware ESX-Server? I has problems with this scenario synchronizing at all with 2.6.x-kernels. Otherwise: Does "ntpdate <your.time.server>" work before ntpd is started? It should set your system time to that of the time server. After starting ntpd: What ist the output of "ntpq -p"? What is the output on "ntptrace"? Try these command for at least 15 minutes after (re)starting ntpd, it takes some time (i.e. is careful) to synchronize. -- Viele Grüße ------------------------------------------------------------------------ Michael Behrens