Yo Hal! On Fri, 15 Sep 2017 15:21:32 -0700 Hal Murray <hmur...@megapathdsl.net> wrote:
> >> I think you should revert the long double change and wait until
> >> post-release to clean up that area - not just the precision part
> >> but the whole clock adjusting area.
>
> > It fixed a bunch of issues and starting over could take weeks.
>
> What problems did it fix?
It fixed many problems with accuracy. I suggest looking at the change logs
if you want details.
> Do you think we need more than microsecond accuracy when making the
> first long jump?
ntpd NEVER had better than micro second accuracy until the change.
Common wisdom said it did, but the precision enhancements in ntpq and ntpmon
showed otherwise.
> Are there other cases when loss of precision happens?
Several. timespec(64) will smoke a lot out.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpJ4obJUHAaH.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
