I don't think you have a clear picture of the architecture of chrony... There is a chrony daemon (chronyd) that performs the actual time sync functions and for that it has to run permanently, and have sufficient privileges to sync the time. It is usually started by systemd when that is the local method to manage services.
Then there is the "chronyc" program which can send queries to a chronyd daemon, which can be on the local system or anywhere else on the network, and it displays the information it gets back from the daemon in user-readable form. It requires no privileges, it does not run as a daemon, it has no involvement with systemd. Of course to meaningfully use chronyc, you need to have a chronyd running elsewhere in your network, and it has to be configured with sufficient privileges to allow chronyc queries from the address where chronyc is used (cmdallow keyword). Rob On 2025-08-04 11:04, Remush wrote: > Hey there again, this might be a weird question but I'm testing my options. > I'm trying to set up a pod in Openshift that will allow me to run `chronyc > sources`. > > Sadly, the Openshift doesn't allow pods access to systemd, in addition it > sets the user to be a random uid, but within the gid of root. > > Is there any way possible to achieve `chronyc sources` without access to the > daemon? > > Sorry for the weird use case, might be irrelevant to this community. > Thanks a lot in advance! -- To unsubscribe email [email protected] with "unsubscribe" in the subject. For help email [email protected] with "help" in the subject. Trouble? Email [email protected].
