My guess was that he was attempting monitoring of an existing chronyd outside his container. I have done that (way) in the past to monitor time service using nagios. I just installed (copied) the chronyc binary to the monitoring system, which itself was running ntpd, and made a check_chrony script that did a chronyc call (from a perl skeleton available for nagios). Probably not the most efficient way, but it works. I used "chronyc tracking", of course with a -h parameter.
But maybe I am completely wrong guessing his objectives... it is not very clear from the explanation. Rob On 2025-08-05 09:20, Mingye Wang wrote: > So uh Rob gave a good explanation of how chrony works, but honestly: > this smells like an "XY problem" to me. What are you attempting to do, > actually, by getting `chronyc sources`? In other words, what > information do you *really* need? >
