On Tue, Apr 08, 2025 at 02:09:44PM -0700, Greg A. Woods wrote: > So if that's right then a changing maxerror means ntpd is constantly > providing a new maxerror value to store.
It does, but on a sane value the value is bound to lower values, and ntpd does sync: associd=0 status=0615 leap_none, sync_ntp, 1 event, clock_sync, pll offset: 0.812757 pll frequency: -54.2365 maximum error: 142.553 estimated error: 0.69 kernel status: pll nano pll time constant: 8 precision: 1e-06 frequency tolerance: 495.911 (all other values are 0) > Maybe the delta in maxerror is just telling us the system clock is > "skewed", i.e. not running at the frequency it claims to run at, which > would not be too surprising. What is suprising is that it happens on a domU but not on another on the same dom0. -- Emmanuel Dreyfus m...@netbsd.org
