Re: [chrony-users] Pool vs. server without config parsing

[Rob Janssen <chrony-users@xxxxxxxxx>]

As far as I understand it, you want to make sure that the configuration of
the sources is syntactically correct, and maybe also that the sources are working.
It should be possible to do that by reading the .sources files (which are easier
to parse than a full chrony.conf) and maybe check if there is a corresponding
(or at least reasonable) number of actual sources in the running chrony.

Other than that, I would not know what you are getting at.

Personally I find it unfortunate that a .sources file can only contain peer, pool and
server directives and not refclock, but for you that is probably a blessing because
refclock would be more difficult to parse and validate.

Rob

On 2024-06-21 18:42, Josef 'Jeff' Sipek wrote:
> On Fri, Jun 21, 2024 at 18:26:06 +0200, Rob Janssen wrote:
>> Maybe you should look at how more recent versions of chrony and the packaging
>> by distributors handle this issue.
> That's exactly how we plan to do things, but we also want a sanity check
> that the configuration and running state match our expectations (system
> upgrades can be very messy when moving from a wild-west scenario to a more
> closely managed config).  Using confdir/sourcedir won't make the "sanity
> check" step go away.
>
> Or am I missing something?
>
> Thanks,
>
> Jeff.
>


-- 
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx 
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.