Re: Clock drift and other open issues: Collecting information
Jan-Benedict Glaw <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.vax |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2023-12-27 16:46:41 -0500, Ken Wellsch <[email protected]> wrote: [...] > It seems like quite a reasonable drift rate to me, and it got here without > a lot of horrible never-ending thrashing like I saw when trying to use > the stock "iburst" rapid convergence tag that does work very well on > "modern" equipment with gigabit NICs and fast networks. My /60 is now downstairs and has network connectivity, with `dhcpcd`, `ntpdate` and `ntpd` started. While it as a stable 100 Hz time (some 2 to 4 seconds drift (being slow) per day), it won't get (or keep for long) NTP synchronization. It may get sync, but offset will get large, loose sync, ... While reading about ntpd, I noticed that it mentions to use 64bit fp values. Also noticed root@lili:/var/cache/git/NetBSD-src/external/bsd/ntp [trunk] # find|grep ieee ./dist/include/ieee754io.h ./dist/libparse/ieee754io.c I haven't really checked the code, but I've got a feeling right now... MfG, JBG --
signature.asc
(application/pgp-signature, 195 B)
-----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCZYy6BwAKCRAdvV51g5nh uzaXAKCJ9TMXRkS824zEuw9ooL2P99B+DwCdGhV2DBH3vOoHmUlog8lzLV3unOw= =zh6v -----END PGP SIGNATURE-----