Gautam Thaker wrote:
On Feb 26, 5:44 am, Dave Hart <[email protected]> wrote:
http://davehart.net/moo/ntpd-QPC-20090614-0900.zip
That represents the last in a series of 4.2.4p6-based private releases
of mine.
OK, so started to use this 4.2.4p6 version and immediately saw a
reduction in variations in the "offset" value.
see graphic at:
http://www.atl.external.lmco.com/projects/QoS/documents/feb26_offset.png
I should note a few things:
1) when i switched to this version of ntpd.exe, the ntpq.exe from
4.2.7p98 did not seem to be able to query the daemon.
I know you use windows but that behavior can be same on other
platforms. I use NetBSD and when I update it is not just the
ntpd binary and full list for my version of NetBSD is:
ntpd, ntp-keygen ntpdate ntpdc ntpq ntptime ntptrace and sntp.
You need all the executables appropriate for the ntp version
and your windows version otherwise you are likely to have
problems.
David
2) Meingberg Time Service Monitor GUI program was reporting status
(presumably since it is based on 4.2.4 ?)
3) I switched to using ntpq.exe from 4.2.4 that comes w/ Meinberg
install and that ntpq.exe worked ok.
4) while the offset reported has become much less wild I noted that
both 'delay' and 'jitter' values reported are ALWAYS now just "0.977".
This should be an indication that something is not right and thus I
don't know if i can trust the improved "offset" value stability.
Any comments welcome.
Gautam
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
