Gonda wrote regarding '[SLE] ntpd seems to work but how well?' on Wed, Sep 01 at 08:11:
I have read the info on ntpd several times and I think I understand the basics. I hope I have ntpd working on my dialup system with 9.1.
One of the possibilities to see if it really works should be to use ntpq -p I get the following output with this command but apart from recognizing the four addresses that I have chosen I do not understand the meaning of the output. Somebody with an explanation in plain English?
# ntpq -p remote refid st t when poll reach delay offset jitter ===================================== 202.180.0.71 .INIT. 16 u - 64 0 0.000 0.000 4000.00 my1.doubleukay. 192.6.38.127 2 u 40 64 1 1039.17 -183.26 0.002 ns01.deu.edu.tr .INIT. 16 u 49 64 0 0.000 0.000 4000.00 darkstar.sanet. 212.82.32.15 2 u 58 64 1 908.414 -82.537 0.002
Your ntp isn't working well, I think. root@newwww:/tmp > ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 4 - 32 64 377 0.000 0.000 0.000 -ntp-0.gw.uiuc.e truechimer.cso. 2 u 35 1024 377 16.029 -0.519 0.152 #gilbreth.ecn.pu molecule.ecn.pu 3 u 32 1024 377 80.024 -3.171 37.271 #harbor.ecn.purd atom.ecn.purdue 4 u 539 1024 377 57.604 16.357 34.192 -molecule.ecn.pu usno.pa-x.dec.c 2 u 541 1024 377 125.504 24.895 0.000 *caesar.cs.wisc. ben.cs.wisc.edu 2 u 10 1024 377 10.708 -0.307 0.121 +milo.mcs.anl.go clepsydra.dec.c 2 u 931 1024 377 58.452 -0.247 0.252 +mcs.anl.gov clepsydra.dec.c 2 u 176 1024 377 58.688 0.221 0.678 wuarchive.wustl 0.0.0.0 16 u - 1024 0 0.000 0.000 4000.00 -dense.utcc.utor tyme.gw.utoront 2 u 536 1024 377 23.569 -4.097 0.000 The line with the * at the beginning is the best peer right now, and the one ntpd is syncing off of. You should have one of those, even with one server: dsauer@danny-pc:/tmp> /usr/sbin/ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *newwww.internal 130.126.24.53 3 u 1000 1024 377 0.512 -0.649 0.359 Anyway, the important columns, IMHO, are st - stratum (there are 2 hosts between a stratum3 host and an atomic clock), offset (the difference in your clock and theirs), jitter (the reliability of that server), the delay (the distance between you and them) the refid (that server's reference). Also, the first char is important. It'll take some ntpd docs that I don't have in' front of me to explain that. You may wanna look at /usr/share/docs/xntpd to get more useful information... --Danny, probably not helping enough