From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id BE2621FF16D for ; Mon, 19 Aug 2024 18:05:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id F0CD01C17C; Mon, 19 Aug 2024 18:05:41 +0200 (CEST) Date: Mon, 19 Aug 2024 17:50:29 +0200 From: Marco Gaiarin To: pve-user@lists.proxmox.com Message-ID: References: <46ebpk-rqm.ln1@leia.lilliput.linux.it> <6f37f0399dca2a68bf3129aefc8a5843799654bd@antreich.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <6f37f0399dca2a68bf3129aefc8a5843799654bd@antreich.com> Organization: Casa Gaiarin User-Agent: Mutt/2.2.12 (2023-09-09) X-SPAM-LEVEL: Spam detection results: 0 AWL 0.367 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_PASS -0.1 DMARC pass policy JMQ_SPF_NEUTRAL 0.5 SPF set to ?all KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [PVE-User] NTP on PVE8... X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE user list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" 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