[PVE-User] NTP on PVE8...
Marco Gaiarin
gaio at lilliput.linux.it
Mon Aug 19 17:50:29 CEST 2024
Mandi! Alwin Antreich
In chel di` si favelave...
> systemd-timesyncd only uses one server to update its time, which can lead to
> time jumps when this NTP can't be accessed reliably. NTPs (eg. ntpd/chrony) are
> usually using 3+ servers to calculate a mean time and compensate for jitter and
> other delays.
systemd-timesyncd does not use one server, have also fallback one (or use
round robin); surely 'mean/compensate' is better then fallback and round
robin, but...
> This allows to keep the time more stable and especially helps
> when Ceph or HA is enabled. ;)
...clearly i'm speaking of standalone server or non-HA, non-Ceph clusters!
Anyway, the statement:
>> WARN: systemd-timesyncd is not the best choice for time-keeping on servers, due to only applying updates on boot.
it is not true: i suggest to remove at least 'due to only applying updates on boot'.
(clearly, for future 'pve8to9' scripts... ;-)
--
More information about the pve-user
mailing list