--- Begin Message ---
Hi,
systemd-timesyncd use of a single source is the main issue. I've had Ceph
clusters go down because one timeserver had gone haywire and the monitors
decided that everyones time was incorrect.
Like lot of systemd-stuff, it is written for Lennard P.'s laptop, not your
average server environment. (Not trying to start a war here, I like a lot of
systemd-stuff, but of some stuff I wonder who was using what substance when
they decided to release/use it :))
--
Mark Schouten
CTO, Tuxis B.V. | https://www.tuxis.nl/
<[email protected]> | +31 318 200208
From: Marco Gaiarin <[email protected]>
To: <[email protected]>
Sent: 2021-10-24 11:27
Subject: [PVE-User] Chrony?!
I've just installed a PVE7; impressive, thanks.
But i've found that Chrony get installed; looking at changelog/roadmap:
https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.0
Time Synchronization:
Due to the design limitations of systemd-timesync, which make it
problematic for server use, new installations will install chrony as the
default NTP daemon.
If you upgrade from a system using systemd-timesyncd, it's recommended
that you manually install either chrony, ntp or openntpd.
But looking at wiki, still systemd-timesyncd is cited:
https://pve.proxmox.com/wiki/Time_Synchronization
What are these «problematic for server use» limitation? Someone can point to
some clue?
Thanks.
--
Il backup è quella cosa che andava fatta prima.
(Proverbio Cinese, Simone Aliprandi)
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
--- End Message ---
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
