* Michael Hirmke
Hi,
[...]
so you probably also have this warning in your journal?
Feb 03 11:12:14 Crash nscd[1043]: 1043 monitoring file `/etc/resolv.conf` (5) ... Feb 03 11:12:47 Crash kernel: Key type dns_resolver registered Feb 03 11:12:47 Crash kernel: NFS: Registering the id_resolver key type Feb 03 11:12:47 Crash kernel: Key type id_resolver registered
all that I see
so it seems, NetworkManager here has some debug mode configured. It was:
NetworkManager[1680]: debug: write_resolv_conf: ' ... ' NetworkManager[1680]: debug: dns settings written to /var/run/netconfig/resolv.conf NetworkManager[1680]: debug: /etc/resolv.conf is a regular file NetworkManager[1680]: ATTENTION: /etc/resolv.conf is not a link to /var/run/netconfig/resolv.conf NetworkManager[1680]: call "netconfig update -f" to adjust /etc/resolv.conf
no, not running NetworkManager on this desktop, wicked. and fwiw, I just updated another desktop and it didn't even create the /var/run/netconfig/resolv.conf. running "netconfig update -f" also failed to create the /var/.. file or the simlink. so I copied /etc/resolv.conf there and created the simlink and ran "netconfig update -f". but it doesn't contain the symlink notice. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org