Well, as I mentioned, there is a valid use case for running chronyc on another system than where chronyd is running, e.g. when you are using chronyd at several places in your network and you want to monitor their behavior on one system, e.g. using nagios or zabbix.
When you want to use chronyc to monitor a local chronyd, your system has to be capable of running that service (daemon), and apparently your solution (which I am not familiar with) is not. So you need to use another solution. Something that can run services. That is also required because chronyc essentially is one-shot, and any useful monitoring of NTP has to be running for a while to average the polls done to other servers. Rob On 2025-08-05 15:31, Remush wrote: > So it means I have to set up something, a vm, a pod, a server, something that > has chronyd running? > It kind of beats the point, no? If I have a place that runs chronyd why not > run chornyc from there? -- 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.
