Thank you for the responses. I just have a few small clarification
questions.
I have used ntpdc and ntpq on the same machine that tries to synch
with an
ntp server (192.168.0.4). The ntp server uses its own system clock
which is
not disciplined (need to figure out how to do that). I am curious as
to why
the reported offsets are different.
ntpdc> peers
remote local st poll reach delay offset disp
==========================================================
=LOCAL(0) 127.0.0.1 5 64 377 0.00000 0.000000
0.03059
*192.168.0.4 192.168.0.20 6 16 377 0.00011 0.007474
0.02922
[EMAIL PROTECTED] etc]# ntpq -p ntp
remote refid st t when poll reach delay
offset jitter
==========================================================
192.168.0.255 .BCST. 16 u - 64 0 0.000
0.000 0.001
*LOCAL(0) .LOCL. 5 l 51 64 377 0.000
0.000 0.001
Also, David, did you mean 100 nano-seconds or 100 micro-seconds? I
would be
totally fine with 100 micro-seconds. Would that be achievable if I
get a GPS
clock for the ntp server and keep the rest of the setup the same?
(These are
Linux 2.6.24 machines). (an info about a cheap Linux compatible clock
would
be greatly appreaciated).
Many Thanks,
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.org/mailman/listinfo/questions
