One more data point -- I changed the timezone settings from Europe/Dublin to Europe/London (we're in the same timezone, after all), and it reduces the error to 1 hour from two. Still have the analog clock fast by 1 hour and the digital one slow by 1. Something in Plasma apparently has it in for folks in GMT... Brendan On 19/11/2018 23:47, Carlos E. R. wrote:
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
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org