From: "Keith" <ac7xc1nx@xxxxxxxxxxx>
Run a cron job for root using
rdate -us 131.107.1.10
see man rdate
Keith, you should be utterly ashamed of yourself for that advise.
The accuracy of rdate is generally extremely poor compared to the
accuracy of a properly ntpd.
Vikram needs to provide some information from his ntp.conf file.
It may be setup wrong. It is also possible he has recompiled his
kernel. There are options that make ntp synchronization very poor.
He also needs to give some "ntpq" information. What do "assoc"
and "ntpq" produce? If assoc does not show the clocks are reachable
or only shows the local host clock we can work from there. He also
should realize that it takes awhile for ntpd to "lock in." Set it
running, go away for coffee or to do something else, then run ntpq
again and see what assoc and peers show. It should look something
like this:
===8<---
ntpq> assoc
ind assID status conf reach auth condition last_event cnt
===========================================================
1 28876 9414 yes yes none candidat reachable 1
2 28877 9414 yes yes none candidat reachable 1
3 28878 9614 yes yes none sys.peer reachable 1
ntpq> peers
remote refid st t when poll reach delay offset
jitter
==============================================================================
+xxxxxxxxxx.xxx. .GPS. 1 u 303 1024 377 43.146 11.990
51.952
+xxxxxxxxxxx.xxx .GPS. 1 u 381 1024 377 32.805 8.901
3.676
*xxxxxxxxx.xxx .PSC. 1 u 116 1024 377 34.538 7.022
1.706
===8<---
Telling someone to use rdate is like telling an ambulence driver to use
a Ford Model T.
{^_^}
