| Re: [chrony-users] sourcedir reload ignores the maxsources option |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] sourcedir reload ignores the maxsources option
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 2 Jun 2025 16:12:19 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1748873544; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sVpFSzvjINZaLcgKm+QTNJ80RgJmTi8/ca17XkhSXrQ=; b=EomAAwskI0qc56AXk3vLqnkes1Xkj9L8+Un75c1H8REaB0YJ44mEZywH0lI4BXqDrD5e96 yenK6FEi65UuiBnNIJjhI3TvBfcS5y+ezhEWfWTIXsjbJWJbiTeHpa62QMxIhYUsoO6EA5 9HogSnFmzn2hPIsmO1Yj7cYVZ+7f4Dk=
On Sat, May 31, 2025 at 07:00:12PM +0200, Vincent Blut wrote:
> chrony 4.6 introduced quite a few changes to the way time sources are
> loaded from sourcedir. It seems, though, that we now have a regression¹
> as the 'maxsources' option is now ignored when reloading sources.
Thanks for forwarding the report. I can reproduce the problem and I
have a fix ready. It's not just pools, it impacts all sources loaded
from a sourcedir not specified by IP address (i.e. those that start
as "unresolved").
The patch will apply cleanly to 4.6(.1) if you would like to add it to
the downstream package. I just need to add a proper test of the
sourcedir directive with runtime changes so a bug like this doesn't
happen again (it requires some improvements in the testing framework
to be able to modify the file during test).
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.