Bug#947936: chrony: Does (still) not start properly on boot on buster

[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.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20200113/351f7a7e/attachment-0001.sig>