>> NetworkManager calls netconfig only for DNS
updates, it does not provide
>> NTP information.
> But why does it state "resolved ntp-policy 'auto'"?
Because this is current value of ntp-policy. It does
not mean someone
provided actual values to fill in NTP servers.
>> Distribution and version you are running,
> openSUSE Tumbleweed.
Oh. You are not newbie on this list to not know that
version are essential to get proper support. So far you just wasted your
and my time.
Sorry for that 8-<
I just wanted to understand the general relationship between the
different pieces. I was not aware of differences between openSUSE
flavours, that use NetworkManager.
1. Tumbleweed changed default NetworkManager DHCP
client to internal.
Which matches your information.
2. Tumbleweed completely broke integration of chrony
with dhclient which
means even changing client to dhclient won't help. It probably works
with wicked now for a change.
So in fact I can uninstall chrony, use systemd-timesyncd and won't lose
So using wicked instead of NetworkManager may work
If you need NetworkManager and feel adventurous you can
a) open NetworkManager upstream bug report about
calling netconfig for
NTP in addition to DNS
b) try NetworkManager with dhclient and if it does not
openSUSE bug report against chrony
Opening bugs against NM in the past led to discussions, why I want/need
the feature in question. So I guess I will avoid that.
c) write NetworkManager dispatcher script to e.g. feed
NTP data to netconfig
Presumably I will go this way.
Thx for your patience.
You seem a little bit upset about the implemention in Tumbleweed!?!
To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org