On 2020-01-13T00:48+0100, Michael Biebl wrote:
Am 13.01.20 um 00:43 schrieb Michael Biebl:Am 13.01.20 um 00:05 schrieb Vincent Blut:On 2020-01-12T23:24+0100, Michael Biebl wrote:Am 12.01.20 um 23:08 schrieb Vincent Blut:We probably should not keep this hack forever, but instead let timedated read known NTP implementation unit names from usr/lib/systemd/ntp-units.d/*.list since this has been reintroduced in systemd 243. I added the necessary bits in chrony 3.5-5.Hm, I don't see how this change in timedate would actually help in this situation. Support for ntp-units.d in timedated/timedatectl just enables that if you use "timedatectl set-ntp true|false" it will prefer alternatives if installed.Doesn’t systemd-timesyncd look for foreign services in ntp-units.d/ when starting? I thought that was the case and that it remained inactive in case an NTP implementation with a higher priority was found there.Reading through the diff at https://github.com/systemd/systemd/pull/13136 that doesn't seem to be the case. ntp-units.d is only used by timedated, not timesyncd.Fwiw, there is this related MR https://salsa.debian.org/systemd-team/systemd/merge_requests/61
I mentioned another bug report about a similar issue with ntp.
Ideally, only one NTP client should be enabled at a time.
Note that we restore timesyncd (if it is enabled) on chrony removal to not wait for the next reboot to get the clock synchronized again, so if having only one NTP client enabled at a time is where we are heading for, then I’ll have to drop that code snippet.
signature.asc
Description: PGP signature
