|
As a point of reference, start out with some known
good, public time servers:
server clock.psu.edu
#server nist1.aol-va.truetime.com DNS fails on this one so IP is below server 205.188.185.33 server tick.uh.edu These work for me.
Next, restart the ntp daemon and give it an hour to
work. It queries the servers rapidly during the first hour and then less often
once the drift is better calculated.
[root@firewall n820131]# ntpq
ntpq> peers remote refid st t when poll reach delay offset jitter ============================================================================== *nist1-aol-va.tr .ACTS. 1 u 755 1024 377 278.192 23.846 32.999 +otc2.psu.edu otc1.psu.edu 2 u 688 1024 377 240.356 -47.237 24.591 +Tick.UH.EDU .USNO. 1 u 796 1024 177 259.760 -20.105 31.740 Your clock will not be corrected / updated
until the first hour passes (at least mine wasn't). And if the clock is WAY off,
you should see an error reported in your /var/log/messages and the ntp daemon
may quit.
Once you get it working, you can select some
new time servers closer to your home location.
|
Title: ntp
- RE: [suse-sparc] ntp Nick Thompson
- RE: [suse-sparc] ntp Ng, Yatsen
