On Tue, Mar 12, 2024 at 08:04:04AM +0000, Filip Verwee wrote: > Dear, > > On our cluster nodes we use node-exporter to collect the timex information > from the kernel. The advantage of using the node-exporter timex collector is > that it is independent of the NTP implementation used on the nodes (ntpd, > chrony...). Unfortunately, it looks like chrony is not updating the timex > kernel offset parameter. Its value is always '0' while on nodes using ntpd, > the timex kernel offset parameter represents the time offset in between local > system and reference clock. > This seems like a shortcoming in chrony. Are there any plans to implement > this functionality in the near future?
That is not possible as chronyd doesn't use the kernel PLL. The closest thing to the kernel PLL offset would be the chronyc tracking offset. -- Miroslav Lichvar -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
