On 2021-08-01 8:47 p.m., Carlos E. R. wrote:
So? Forget yast and configure ntp by hand, it is not that difficult.
I have not looked, but it is possible that yast is designed today to handle only chrony, while in the past it would only handle ntpd. You could have a look in YaST to see if you can tell YaST to configure ntpd instead.
Since chrony is now default, maybe Yast should have been properly updated. Leaving it this way creates a mess, where you're not sure what's happening. With chrony, the only way to set a server appears to be editing either chrony.conf or pool .conf. There doesn't seem to be anything in Yast, where one might expct settings to be. Sure, it's easy enough to edit files, but that requires knowing about those files. There are many situations where a local server is supposed to be used, such as in business networks, so hiding the config is not a good idea. I run into similar with my Asus table. The NTP server is somewhere in Asia and there doesn't appear to be any way to change it. My solution was to create a DNS alias to send it to my server. If you're going to create a default server, make it pool.ntp.org and nothing else. It uses geolocation to use a reasonably nearby server. I have no idea where opensuse.pool.ntp.org is located, but I bet it's not in Canada. The stratum 1 servers I connect to are located in Toronto, which is the next city over (in fact, located in the building where I worked for 17 years).