On Samstag, 11. März 2023 14:02:42 CET Andrei Borzenkov wrote:
On 11.03.2023 15:47, mh@mike.franken.de wrote:
What's confusing me, is that netconfig seems to rely on getting ntp information from nm!?!?
You seem to believe that netconfig was developed for NetworkManager. netconfig existed long before NetworkManager in SLE. NetworkManager is just one of possible source of information.
No, this is not what I believe. I know that netconfig is much older, because I use SuSE Linux for at least 25 years.
At least the ntp-config module tries to read it from NetworkManager.netconfig.
ntp-config tries to read from the sources according to the configured policies. Default policy if NetworkManager is active includes information from NetworkManager. Whether NetworkManager actually provides any meaningful data for this specific netconfig module is entirely different question. You can redefine netconfig NTP policy to omit NetworkManager (or to ignore NTP completely).
This is all documented in "man 8 netconfig".
I know this and I read this man page among dozens of other documents including the nm docs on the website. But obviously I can't express myself correctly 8-<
This is the reason, why I now asked on an openSUSE list instead of the nm list.
Well, actually *this* is the question for NetworkManager. NetworkManager does not have any framework for managing dynamic NTP informational at all, so there is no way to feed it to netconfig. It has to be implemented in NetworkManager first.
Why is this the question for nm? The question for me is, why netconfig relies on a value from NetworkManager.netconfig, that is never provided? What makes netconfig believe it can get the value from there, if it is a known fact, that the necessary enhancement never made it to nm? Bye. Michael.