• Re: Just verified chrony.conf -> cond.f/* still not fixed in unstable,

    From Vincent Blut@21:1/5 to Tim Connors on Wed Mar 26 11:43:34 2025
    Copy: 1073865@bugs.debian.org
    Copy: maney@two14.net (maney)

    Le 2025-03-26 14:20, Tim Connors a écrit :
    Hi maintainer,

    This is a rather unfortunate bug. As can be seen from the manpage,

    "Generally, the directives can occur in any order in the file and if a
    directive is specified multiple times, only the last one will be
    effective. Exceptions are noted in the descriptions."

    One of the potentially many configurations an end-user may need to adjust
    is makestep, which is configured almost last in chrony.conf.

    All VM's for instance, will need to customise that, so makes sense to
    drop into /etc/chrony/conf.d/vm.conf:

    # ensure chrony doesn't bail if vmware gains or loses too many ticks
    makestep 1 -1

    Well that's unfortunate, isn't it? I now need to manually munge /etc/chrony/chrony.conf of all of my generations of VMs. And anything
    else I've customised, I need to keep track of which of my machines are VMs and which are not.

    I just verified this *isn't* an upstream bug, with upstream not having included a confdir directive at all. It's also not fixed in 4.6.1-1 in unstable.

    It will be fixed soon.

    It would be extremely nice to have this fixed for trixie. It's
    unfortunate that chrony is a regression over what we had with NTP, given
    it is the claimed replacement of NTP and NTP fixed this issue 20 years
    ago.

    Don't use it, then!

    -----BEGIN PGP SIGNATURE-----

    iHUEABYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCZ+PaVgAKCRAQn1qAt/bg AfQDAQCpAxnOd0y+Eq3BfH1Yv2qlRu+nvNM3t8FE7FfLSym9qAEA3L6RzOI+GSRo Fz3w9q6ToVjfQd4CQhO5/JPlCfMEyAs=
    =S/Ss
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)