timemaster: fix PTP poll configuration for timemaster >=4.2 #684
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dupremathieu
approved these changes
Jan 10, 2025
When using timemaster >= 4.2 (currently in Debian Sid), the chrony config looks like: refclock SOCK /var/run/timemaster/chrony.SOCK0 poll 2 filter 4 refid PTP0 precision 1.0e-9 delay 1.0e-09 poll 0 The double poll definition triggers a weird behavior in chrony: PTP is poll'd every 4s but the Reach/LastRx computation expect a poll every second. This makes the PTP source looks unreliable (wrongly). Fix this by using the proper config to setup the PTP poll period "ntp_poll" (sic) New config look like: refclock SOCK /var/run/timemaster/chrony.SOCK0 poll 0 filter 4 refid PTP0 precision 1.0e-9 delay 1.0e-09 Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
insatomcat
force-pushed
the
yco/timemaster_debian_13
branch
from
9ccf0a9 to
3b57e54
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using timemaster >= 4.2 (currently in Debian Sid), the chrony config looks like:
The double poll definition triggers a weird behavior in chrony: PTP is poll'd every 4s but the
Reach/LastRxcomputation expect a poll every second. This makes the PTP source looks unreliable (wrongly).Fix this by using the proper config to setup the PTP poll period "
ntp_poll" (sic)New config look like: