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 702121FF16D for ; Mon, 19 Aug 2024 11:09:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D44DD12EFD; Mon, 19 Aug 2024 11:10:06 +0200 (CEST) From: Marco Gaiarin Date: Mon, 19 Aug 2024 11:00:22 +0200 Organization: Il gaio usa sempre TIN per le liste, fallo anche tu!!! Message-ID: <46ebpk-rqm.ln1@leia.lilliput.linux.it> X-Trace: eraldo.lilliput.linux.it 1724058035 8055 192.168.1.45 (19 Aug 2024 09:00:35 GMT) X-Mailer: tin/2.6.4-20240224 ("Banff") (Linux/6.8.0-40-generic (x86_64)) X-Gateway-System: SmartGate 1.4.5 To: pve-user@lists.proxmox.com X-SPAM-LEVEL: Spam detection results: 0 AWL 0.323 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 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: [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 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-user-bounces@lists.proxmox.com Sender: "pve-user" Running 'pve7to8' i've catch: INFO: Checking for supported & active NTP service.. WARN: systemd-timesyncd is not the best choice for time-keeping on servers, due to only applying updates on boot. While not necessary for the upgrade it's recommended to use one of: * chrony (Default in new Proxmox VE installations) * ntpsec * openntpd This is indeed mostly true, and in a cluster using a NTP daemon is a must. No doubt on that. But for a standalone server, systemd-timesyncd seems sufficient to me; and surely NOT 'only applying updates on boot': systemd-timesyncd sync time at regilar interval! PollIntervalMinSec=, PollIntervalMaxSec= The minimum and maximum poll intervals for NTP messages. Polling starts at the minimum poll interval, and is adjusted within the specified limits in response to received packets. Each setting takes a time span value. The default unit is seconds, but other units may be specified, see systemd.time(5). PollIntervalMinSec= defaults to 32 seconds and must not be smaller than 16 seconds. PollIntervalMaxSec= defaults to 34 min 8 s (2048 seconds) and must be larger than PollIntervalMinSec=. Here still using systemd-timesyncd for my standalone servers... -- _______________________________________________ pve-user mailing list pve-user@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user