Add maxdistance parameter to chrony #134
Conversation
|
Hi @geerlingguy is there something I can do to get this PR merged? |
|
@geerlingguy It should be fine now. I update the readme & the param name |
|
@geerlingguy I fixed the yaml lint syntax! |
|
@geerlingguy What's the issue ? |
|
Looks like build failures due to the docker python library |
|
Hi @geerlingguy, do you plan to fix this issue ? Thanks! |
|
This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution! Please read this blog post to see the reasons why I mark issues as stale. |
README.md
Outdated
| @@ -66,6 +66,12 @@ Whether to restart the cron daemon after the timezone has changed. | |||
|
|
|||
| Enable tinker panic, which is useful when running NTP in a VM. | |||
|
|
|||
| ntp_tinker_panic: true | |||
There was a problem hiding this comment.
The ordering of these descriptions and examples is off, the ntp_chrony_maxdistance should be up here.
There was a problem hiding this comment.
Can you check now, it shoudl be good, Thanks !
This pull request allow users to edit
maxdistanceparam in chrony config.It usefull to fix the issue when the distance with the source is greater than the default value (3)