Den 2018-03-26 kl. 22:58, skrev Brüns, Stefan:
On Montag, 26. März 2018 22:17:46 CEST Larry Finger wrote:
On 03/26/2018 03:00 PM, Patrick Shanahan wrote:
* Brüns, Stefan
[03-26-18 15:37]: On 03/26/2018 02:15 PM, Linux Kamarada wrote:
2018-03-23 13:12 GMT-03:00 Michal Kubecek
: On Montag, 26. März 2018 21:07:59 CEST Ken Schneider - Factory wrote: 3. It will stop Networkmanager and/or wicked from doing any updates in the future. I have not experienced this. Nor have I. What is the justification for #3 above? It seems to me that as long as you have a nameserver that works, all updates should work. In addition, doesn't PackageKit and/or zypper control updates? /etc/resolv.conf is a file generated at runtime using netconfig (called by NetworkManager/wicked). netconfig checks if the file has been been modified and stops updating the file, if not run with the -f parameter.
Or more precisely netconfig update -f If you use nm and see logs like this: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... You can find my version in /etc/resolv.conf.netconfig ... It's not updated. Check with: journalctl _COMM=NetworkManager or journalctl _COMM=NetworkManager | grep resolv.conf Cheers, -- /bengan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org