Miroslav Lichvar pushed to branch master at chrony / chrony
Commits: 27659117 by Miroslav Lichvar at 2024-04-29T11:21:45+02:00 ntp: improve copying of server status When a server specified with the copy option responds with an unsynchronized status (e.g. due to selection failure), reset the source instance to immediately switch the local reference status instead of waiting for the source to become unreachable after 8 polls. - - - - - 1affd03c by Miroslav Lichvar at 2024-04-30T15:52:18+02:00 sources: reorder unsynchronised source status In the source selection, check for the unsynchronized leap status after getting sourcestats data. The unsynchronized source status is supposed to indicate an unsynchronized source that is providing samples, not a source which doesn't have any samples. Also, fix the comment describing the status. Fixes: 4c29f8888c76 ("sources: handle unsynchronized sources in selection") - - - - - c43efccf by Miroslav Lichvar at 2024-04-30T15:52:18+02:00 sources: update source selection with unreachable sources When updating the reachability register of a source with zero, call the source selection even if the source is not the currently selected as the best source. But do that only if all reachability bits are zero, i.e. there was no synchronized response for last 8 polls. This will enable the source selection to log a message when only unreachable sources are updating reachability and it decreases the number of unnecessary source selections. - - - - - 84d6c7a5 by Miroslav Lichvar at 2024-05-02T12:51:38+02:00 sources: allow logging one selection failure on start Allow one message about failed selection (e.g. no selectable sources) to be logged before first successful selection when a source has full-size reachability register (8 polls with a received or missed response). This should make it more obvious that chronyd has a wrong configuration or there is a firewall/networking issue. - - - - - adaca0ff by Miroslav Lichvar at 2024-05-02T14:43:46+02:00 reference: switch is_leap_close() from time_t to double Avoid undefined behavior in the timestamp conversion from double to time_t in REF_IsLeapSecondClose() with NTP sources configured with a large offset correction. - - - - - ebfc676d by Miroslav Lichvar at 2024-05-02T14:43:51+02:00 ntp: limit offset correction to supported NTP interval When an NTP source is specified with the offset option, the corrected offset may get outside of the supported NTP interval (by default -50..86 years around the build date). If the source passed the source selection, the offset would be rejected only later in the adjustment of the local clock. Check the offset validity as part of the NTP test A to make the source unselectable and make it visible in the measurements log and ntpdata report. - - - - - 13 changed files: - doc/chrony.conf.adoc - doc/chronyc.adoc - ntp_core.c - reference.c - sources.c - test/simulation/008-ntpera - test/simulation/118-maxdelay - test/simulation/119-smoothtime - test/simulation/122-xleave - test/simulation/126-burst - test/simulation/127-filter - test/simulation/144-monoroot - test/system/007-cmdmon View it on GitLab: https://gitlab.com/chrony/chrony/-/compare/989ef702aa75be972af432e1dd0fa2038ebad9a5...ebfc676d745545869cbabef55e81e33a94e239ea -- View it on GitLab: https://gitlab.com/chrony/chrony/-/compare/989ef702aa75be972af432e1dd0fa2038ebad9a5...ebfc676d745545869cbabef55e81e33a94e239ea You're receiving this email because of your account on gitlab.com.
