Miroslav Lichvar

That's better. I'm not sure if it's clear enough that it's the command-line options. I suspect someone could confuse it with the systemd service settings.

Clients normally accept leap second information from their servers. The leapsectz option is mainly useful to set the TAI-UTC offset of the system clock. A potential issue is incompatibility with...

A warning about imcompatibility with leapsmearing servers would be nice. However, I don't like the chrony-specific variable name. Would something like local_leap_source as a boolean work better? This would open...

Would it make sense to support a new variable in the server specification for DNS SRV? Or maybe just specify _ntp._udp.* names as hostnames and let the role translate them...

The problem is in the rpm command used to get the package version. It would be weird if it worked on Ubuntu :). If there is a module that can...

chronyd normally runs under a non-root user, so the client's socket needs to have permissions or ownership set in such a way that chronyd will be able to write to...

`/run/chrony` should be accessible only to the chrony group, so I don't think changing group on the socket would do anything. To me it seems like an unnecessary complication.

What frequency does `chronyc tracking` report? If it's larger than 500 ppm, ntpd wouldn't be able to compensate for it. It would most likely be a kernel misconfiguration/bug, causing the...

No, chrony doesn't depend on libchrony. It's only for monitoring and doesn't support all the commands that chronyd and chronyc support.

Thanks for the feedback. I'm planning to make a libchrony release soon. I think I just need to add some documentation to the header. Then I'll submit a new package...