On Mon, Jan 02, 2023 at 12:22:56PM +0000, Bernstein, Amit wrote: > As both source timestamp (NTP and PHC) are very close to each other > And according to chrony faq: "It will let the clock run free for as long as > its estimated error (in terms of root distance) based on previous > measurements is smaller than the estimated error of the second source, and > there is still an interval which contains some measurements from both > sources." > Chrony should have replaced the source from PHC to NTP after no more than > several msec, I have waited about an hour and still saw chrony getting > stucked on PHC source.
Please post output from chronyc sources, sourcestats, ntpdata, selectdata. -- Miroslav Lichvar -- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
