On 20/11/2018 00.04, David C. Rankin wrote:
On 11/19/2018 01:48 PM, Brendan McKenna wrote:
Did that, and it reports the service as being inactive. The timedatectl command still shows Network time on: yes and NTP synchronized: yes, although I'm not certain whether the one affects the other.
They do and should not both be active. I don't think one conflicts with the other, I think the problem is any update by systemd-timesyncd will cause issues with the ntp 'driftfile' if time updates occur when both are enabled. (and ntp my cause the same issue with however timedatectl tracks the clock slew)
Yes, they do conflict. They all try to adjust the same clock and interfere one with another, because they then do wrong calculations. They may not say anything about the problem, they may not know anything about the other one running (they should!), but the condition may create strange symptoms and errors. Use only one of: systemd time, ntpd, chrony -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.0 (Legolas))