From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] NTP on PVE8...
Date: Mon, 19 Aug 2024 17:50:29 +0200 [thread overview]
Message-ID: <ZsNpxeqhqiXNExkN@sv.lnf.it> (raw)
In-Reply-To: <6f37f0399dca2a68bf3129aefc8a5843799654bd@antreich.com>
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... ;-)
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-08-19 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 9:00 Marco Gaiarin
2024-08-19 14:57 ` Alwin Antreich via pve-user
[not found] ` <6f37f0399dca2a68bf3129aefc8a5843799654bd@antreich.com>
2024-08-19 15:50 ` Marco Gaiarin [this message]
2024-08-19 16:34 ` DERUMIER, Alexandre
2024-08-19 18:45 ` Olivier Benghozi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZsNpxeqhqiXNExkN@sv.lnf.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox