Op vrijdag 2 februari 2018 14:03:17 CET schreef Per Jessen:
Peter Suetterlin wrote:
Per Jessen wrote:
With Leap15 switching to chrony instead of ntp, I thought I would play around with it, see if it is really up to it. Just playing, I have no intention of switching.
Learning is always good :) Is chrony a replacement for ntp as server, or client only?
It looks to me to be both. Not a drop-in replacement for ntp, but close.
In the latter case: I've switched my desktop to systemd-timesyncd since a few weeks or so, and removed ntp. It's quite inconspicuous, I can't tell if it works with ipv6 though, my servers are ipv4 only....
ntp is such a solid part of our infrastructure, I don't see any point in switching, only effort. Also, chrony does not appear to have support for hardware reference clocks, which is a bit odd. I may have misunderstood.
systemd-timesyncd is especially usefull on systems without a hardware clock with battery. It also lacks the server capability. In my view chrony has some extended functionality above ntp, but only few need that. Most systems only need the client functionality. More information on chrony: https://chrony.tuxfamily.org/ -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org