Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add maxdistance parameter to chrony #134

Merged
merged 6 commits into from
Dec 16, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,10 @@ Whether to restart the cron daemon after the timezone has changed.

Enable tinker panic, which is useful when running NTP in a VM.

ntp_chrony_maxdistance: '3'

Increase the maximum root distance between the host & the ntp source.

## Dependencies

None.
Expand Down
2 changes: 2 additions & 0 deletions defaults/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -25,3 +25,5 @@ ntp_restrict:
ntp_cron_handler_enabled: false

ntp_tinker_panic: false

ntp_chrony_maxdistance: '3'
3 changes: 3 additions & 0 deletions templates/chrony.conf.j2
Original file line number Diff line number Diff line change
Expand Up @@ -41,3 +41,6 @@ logdir /var/log/chrony

# Select which information is logged.
#log measurements statistics tracking

# sets the maximum root distance of a source to be acceptable for synchronisation of the clock.
maxdistance {{ ntp_chrony_maxdistance }}
Loading