Carlos E. R. wrote:
On 2018-02-02 12:57, 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? 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....
(sorry for semi-OT)
So, we have now three "clock sync" methods?
Nothing wrong with choices, I'd say ;^>
ntp chrony systemd-timesyncd
I see the later good only to sync desktop machines to a time source in the office server or outside. As client. If the intention is to serve the time, then use ntpd.
Chrony is unknown to me.
Same here, but the comparison link Per posted is quite interesting. E.g., as client chrony seems more flexible in adjusting larger deviations. I've had ntp failing to properly sync because of that... For sure there must be a reason the switch is done... (and maybe it's a better choice than the intended firewall switch :o - SCNR) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org