| Re: [chrony-users] Checking chrony.conf for syntax errors |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Checking chrony.conf for syntax errors
- From: Bryan Christianson <bryan@xxxxxxxxxxxxx>
- Date: Mon, 9 Mar 2020 21:54:55 +1300
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smtpcorp.com; s=a1-4; h=Feedback-ID:X-Smtpcorp-Track:Message-Id:To:Date: Subject:From:Reply-To:Sender:List-Unsubscribe; bh=HNBMJO/NbWIpZOt36eBzzp4dVB5qd135hHziXXrYY5M=; b=di4//tUacG108D570xPlJHecnp 4XrLh8cg2t2IQm6HMY4nFMoneYiFcv/LLY/4/j5aqUDQeyvAuPEPa/1lurudWIqu3aG480/phTtD+ jbtB6RubihfQs0cpAQSsiy4VHgP/hDbZ3JaAF661F0deCD3qeQZDNnzvl65LpyE+3r7CQQJ1X6UYc 4Byb+At2/1YCIPLJj8bVfhNRmdZzm3syvEL78KwwVxPXx9dy4fig8QX1a0XdchhdWVeibBUWL+TDv nhg2UnwdS1OVh/I1j/XV6MYoID5P3RI0niU25LgS5s9QyrffqF//6HZVIMxGAUZOZvG5rOTdIdmsR s33/GP+g==;
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=whatroute.net; i=@whatroute.net; q=dns/txt; s=s149811; t=1583744107; h=from : subject : to : message-id : date; bh=HNBMJO/NbWIpZOt36eBzzp4dVB5qd135hHziXXrYY5M=; b=hpeJJfKOmzerVbqdQRIy+vP7QNEW4mx0AYRlq1iijWaC4qDG3mzNDBW5dFl9IzEXcyoguH +BEH/uG3fQbdXd+cNSGdNofeFohtBllcEzd3WnPgLi07RTrYptbPwhlZ6KdMpkeFGdXj+RYQ 3Zc7qS8PWCQfvkC3/NACtql33tchgzKyOkLHIltov6uDasGXZvRzQN5Mn/x4HZfI5ZT3198Q 1vyyGcxq+cF63ewnpoq2B9hIIuSCgoUXG4s3xxwE+h1Y2bpMS+oS0ZxTnl9UlDzb5V4pFgFM vHe3QYY2y64FXaM2huOqRN4mOQEDP8ZHfToCv5j9Rw/Ip/KdBIUaESEA==
- Feedback-id: 149811m:149811acx33YQ:149811s071-kJ4Y3
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
bryan@xxxxxxxxxxxxx
--
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.