Package: chrony
Version: 4.3-2+deb12u1
Severity: normal

User experience: use confdir fragments happily for, say, setting up the
server allow and bindaccess directives.  But confdir fragments don't work
for other things, such as changing the logdir.  :-(

As the chrony docs mention, when a directive appears more than once, the
last instance is the one that takes effect (there are a few exceptions that
accept multiple occurences).  Thus directives in confdir files will be
overridden by the matching directives in chrony.conf.  This issue applies
from bullseye through the current salsa git repository code.

Resolution: move the confdir directive to the end of chrony.conf; alternately,
finish the migration to an all-fragmented config for chrony, as was perhaps
the original intention (I'm thinking of unbound's setup, which I have worked
with in the past).


-- System Information:
Debian Release: 12.5
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 6.7.12+bpo-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chrony depends on:
ii  adduser              3.134
ii  init-system-helpers  1.65.2
ii  iproute2             6.1.0-3
ii  libc6                2.36-9+deb12u7
ii  libcap2              1:2.66-4
ii  libedit2             3.1-20221030-2
ii  libgnutls30          3.7.9-2+deb12u2
ii  libnettle8           3.8.1-2
ii  libseccomp2          2.5.4-1+b3
ii  tzdata               2024a-0+deb12u1
ii  ucf                  3.0043+nmu1

chrony recommends no packages.

Versions of packages chrony suggests:
ii  bind9-dnsutils [dnsutils]  1:9.18.24-1
ii  dnsutils                   1:9.18.24-1
pn  networkd-dispatcher        <none>

-- no debconf information

Reply via email to