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) Other than that -- I don't think they conflict, more it is just incompatible to have both running. Both will sync to the correct date/time, so they are not in conflict there -- but it one applies an update to the clock, it is likely to screw up how the other keeps track of the clock drift. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org