Re: Chrony without daemon

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?

If you just want to know how some sources are doing without knowing
how the system's chronyd is doing with it, you can just run your own
copy of chronyd with `chronyd -U -x`. This way it won't try to do
anything to the system clock, but it still keeps track of its own
concept of the current time by communicating with the servers you
have.

If you want to know what the system's chronyd is doing, then you don't
need root permissions either: you can test it by just running `chronyc
sources` from an ordinary non-root user outside of the container. This
is because chronyc can connect to chronyd in two ways, either the Unix
socket file (which allows for making changes and, on the default
permission setting, requires root [but perhaps you can chmod it]) or
the localhost UDP control port (defaults to 323). You can simply set
your container up to have access to either the file or the port.

Sincerely,
Mingye Wang (Artoria2e5)

-- 
To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "unsubscribe" in the subject.
For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org 
with "help" in the subject.
Trouble?  Email [email protected]