Bugzilla – Bug 1113641
chrony not enabled by default
Last modified: 2018-11-14 14:51:10 UTC
I did a fresh Tumbleweed installation on 2018-10-04 (with the KDE default pattern), and after a few weeks I noticed that the clock was running out of sync.
The reason: chrony was installed, but disabled.
It should be enabled by default to ensure that the clock stays in sync.
In case it's relevant: I did not provide the wifi password during the installation, therefore the installer didn't have internet access. After the installation, I did of course set up the wifi connection ;-)
If you need the YaST logs or other logs, please tell me.
As a sidenote: someone on the opensuse-factory ML proposed to enable systemd-timesyncd instead. That might be an alternative solution. I'll let you decide if you simply enable chrony by default, or if you want to fight that out with the systemd maintainers ;-)
Created attachment 787588 [details]
Josef asked for y2logs on the mailinglist - here they are ;-)
I just did a fresh installation of Snapshot20181112 in a VM and couldn't reproduce it.
During installation I checked the NTP dialoge and found that running the service was preselected. After the first boot I verified that chronyd was running and had synced the local clock to an ntp server.