This is an automated email from git. It was generated because a ref change was pushed to the "chrony/chrony.git" repository.
The branch, master has been updated via 7a032062223853dfa9a1ba67995d3088d0dd7f43 (commit) via b86c50bb9f9062e1a02a8f35bd22b079dd5fdda9 (commit) via 36f9b24dfed2f16ba4929efcb62e658925cdc8aa (commit) via e0b75b87bf2b9e24a0854356c3da3b72aaaae96e (commit) via 6661a614864940611f36b41be39400e0d1ef506b (commit) from bc7629175025ed1c7cf6458a0cdc79c67d9247fe (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 7a032062223853dfa9a1ba67995d3088d0dd7f43 Author: Miroslav Lichvar <mlich...@redhat.com> Date: Wed Jun 21 11:27:41 2023 +0200 doc: update NEWS commit b86c50bb9f9062e1a02a8f35bd22b079dd5fdda9 Author: Miroslav Lichvar <mlich...@redhat.com> Date: Tue Jun 20 16:23:34 2023 +0200 ntp: refresh IP addresses periodically Refresh NTP sources specified by hostname periodically (every 2 weeks by default) to avoid long-running instances using a server which is no longer intended for service, even if it is still responding correctly and would not be replaced as unreachable, and help redistributing load in large pools like pool.ntp.org. Only one source is refreshed at a time to not interrupt clock updates if there are multiple selectable servers. The refresh directive configures the interval. A value of 0 disables the periodic refreshment. Suggested-by: Ask Bjørn Hansen <a...@develooper.com> commit 36f9b24dfed2f16ba4929efcb62e658925cdc8aa Author: Miroslav Lichvar <mlich...@redhat.com> Date: Tue Jun 20 15:28:07 2023 +0200 doc: remove out-of-date statement in server description chronyc refresh no longer forces replacement of sources. Fixes: b2dac47c8267 ("ntp: avoid unneccessary replacements on refresh command") commit e0b75b87bf2b9e24a0854356c3da3b72aaaae96e Author: Miroslav Lichvar <mlich...@redhat.com> Date: Mon Jun 19 16:46:10 2023 +0200 ntp: remove resolving timeout in finalization Don't assume NSR_Finalise() can be called only on exit when the scheduler is finalized. commit 6661a614864940611f36b41be39400e0d1ef506b Author: Miroslav Lichvar <mlich...@redhat.com> Date: Mon Jun 19 16:10:45 2023 +0200 sched: reset timer queue in finalization Don't leave dangling pointers to timer queue entries when they are freed in the scheduler finalization in case some code tried to remove a timer later. Fixes: 6ea1082a72d8 ("sched: free timer blocks on exit") ----------------------------------------------------------------------- Summary of changes: NEWS | 3 +++ conf.c | 13 ++++++++++++ conf.h | 2 ++ doc/chrony.conf.adoc | 17 ++++++++++++--- ntp_sources.c | 50 ++++++++++++++++++++++++++++++++++++++++++++- sched.c | 2 ++ test/simulation/147-refresh | 28 +++++++++++++++++++++++++ 7 files changed, 111 insertions(+), 4 deletions(-) hooks/post-receive -- chrony/chrony.git -- To unsubscribe email chrony-dev-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.