Re: [chrony-users] Checking chrony.conf for syntax errors

[ Thread Index | Date Index | More Archives ]

Thank you Miroslav

> On 9/03/2020, at 9:03 PM, Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
> On Mon, Mar 09, 2020 at 09:38:35AM +1300, Bryan Christianson wrote:
>> I would like to check the chrony.conf file for syntax errors before replacing the working copy of the file
> There are other error messages in the parser. You can search for LOG_FATAL in
> conf.c if you want to match them all.

I'll just look for the 'Fatal error' string in the output.

> Please note that a syntactically valid file doesn't mean chronyd will
> not abort on start. There could unsupported directives, missing
> refclocks, or insufficient permissions.

I knew that was the case but think it would be good to try to catch silly typos and the like before attempting to restart chronyd.

>> If I do this while chronyd is running will it cause any problems with the running instance?
> I think it could if it has the root/chrony permissions, e.g.
> overwritten driftfile, new entries in log files, reconfigured
> timestamping, etc.

Ok - thanks - I hadn't considered the case where the user actually owns the logs etc. I guess if after making a change they start seeing weird behaviour, then they are back to looking in the syslog to figure it out.

Bryan Christianson

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.

Mail converted by MHonArc 2.6.19+