Daniel,
I don't see any productive process in responding to your message other
than to suggest you read the available documentation. The four
timestamps are developed at very specific events in the protocol
operations and you have to interpret the time and other data with
respect to the operations involved. If this is "unfair", that indeed is
the case. If the issue is about actual accuracy versus the clock
discipline algorithm, I have no definitive advise other than to study
the design in the available documentation.
Dave
Daniel Kabs wrote:
Hello David!
> As to which timestamp is "correct" you will need to read the
> architecture briefing on the NTP project page.
That's not fair. I just wanted to use NTP as a tool to measure the time
drift of my system clock and now you pull the dreaded "read the
architecture briefing" weapon on me. What have I done to you to deserve
this? :-)
> While at it, understand
> the raw offset measurement does not reflect the actual clock offset,
> as the latter is determined by the clock discipline algorithm
> described in the briefings on the project page. [...]
You are talking about "clock discipline". That's confusing me as I am
running ntpd using option "disable ntp" which (according to your
implementation documentation) should disable time and frequency discipline.
Cheers
Daniel
_______________________________________________
questions mailing list
[email protected]
https://lists.ntp.isc.org/mailman/listinfo/questions
