You are not logged in.
I've installed openntpd from the community repo. When I run it, it notes that my clock is off and says it is fixing it, but nothing changes - the error remains...
[root@nikolai karam]# timeout 2m ntpd -s -d
ntp engine ready
reply from 207.171.30.106: offset -54.553813 delay 0.073591, next query 7s
reply from 209.237.247.192: offset -54.551548 delay 0.085413, next query 6s
reply from 209.237.247.192: offset -54.548834 delay 0.085137, next query 8s
reply from 209.237.247.192: offset -54.544734 delay 0.085042, next query 6s
peer 209.237.247.192 now valid
reply from 209.237.247.192: offset -54.541780 delay 0.085376, next query 6s
reply from 209.237.247.192: offset -54.538891 delay 0.084944, next query 5s
reply from 209.237.247.192: offset -54.536704 delay 0.085478, next query 8s
reply from 209.237.247.192: offset -54.532551 delay 0.084872, next query 33s
reply from 207.171.30.106: offset -54.525022 delay 0.074086, next query 5s
reply from 207.171.30.106: offset -54.522214 delay 0.073090, next query 9s
no reply from 153.16.4.134 received in time, next query 608s
reply from 209.237.247.192: offset -54.516688 delay 0.084956, next query 34s
adjusting local clock by -54.532551s
interval 0.000 skew 0.000 total skew 0.000
peer 207.171.30.106 now valid
reply from 207.171.30.106: offset -54.517590 delay 0.073218, next query 5s
reply from 207.171.30.106: offset -54.515157 delay 0.072737, next query 9s
reply from 207.171.30.106: offset -54.510606 delay 0.073301, next query 6s
reply from 207.171.30.106: offset -54.507862 delay 0.072833, next query 30s
reply from 209.237.247.192: offset -54.500657 delay 0.085332, next query 30s
ntp engine exiting
dispatch_imsg in main: pipe closed
Lost child: child exited
Terminating
[root@nikolai karam]#
Note that it says "adjusting local clock by -54.532551s and then 3 lines down, the offset is still 54 seconds! Does anyone have any ideas? Maybe openntpd doesn't have permissions to change the clock or something...?
Last edited by tony5429 (2010-07-29 15:41:02)
Offline
Ahh; I just figured it out. So it is not actually adjusting it the full 54 seconds. Rather it is adjusting it to a slightly smaller offset from the correct time each time,
[root@nikolai karam]# ntpd -s -d 2>&1 | grep adjusting
adjusting local clock by -54.090300s
adjusting local clock by -54.062971s
adjusting local clock by -53.985725s
adjusting local clock by -53.902570s
Smart software.
Offline
The above is also explained in the NTPD man-page and the Wiki, please always exhaust those resources first before opening a forum thread.
ᶘ ᵒᴥᵒᶅ
Offline
So it is not actually adjusting it the full 54 seconds.
Then the silly software is talking garbage, by mis-stating what it is doing. So the program should be fixed. I suggest it says:
adjusting local clock by -54.090300s extremely slowly
Offline
tony5429 wrote:So it is not actually adjusting it the full 54 seconds.
Then the silly software is talking garbage, by mis-stating what it is doing. So the program should be fixed. I suggest it says:
adjusting local clock by -54.090300s extremely slowly
I agree. Output should mention that it will be adjusted by -54.090300s in xx second increments, or something.
Offline
Yeah I had read through the wiki page but that output really through me for a loop. To me it would make a lot more sense to have "adjusting local clock to -54.090300s offset."
Offline