On 2018-08-19 22:19, don fisher wrote:
On 08/19/2018 09:06 AM, Patrick Shanahan wrote:
fwiw, it appears yast fails to edit /etc/sysconfig/network/config and maybe that is causing the failure message. I just took the time to edit /etc/sysconfig/network/config and regenerated /etc/resolv.conf using netconfig update -f
will watch for subj "error" message.
Please let me know what you find. I executed the netconfig update command and the only difference between the existing and new resolve.conf files was the elimination of the comment # hsd1.az.comcast.net is my domain name assigned by Comcast. Hard to see that this would make a big difference, but who knows?
Typically, networkmanager writes that file dynamically from its own configuration, or from the information obtained from the router via dhcp. Most often it would be the configuration reccomended by your ISP. As the user can select several network configurations on a click, it makes sense to change the file automatically. The idea is also that if you edit that file manually because you want a different configuration, then it leaves the file alone and writes a message to the log. Also there is a token line in the file to flag to NM that "yes, I know what I did, do not tell me about it", but does not work. Sometimes, apparently, it thinks the file was modified by a human when it was not. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)