Stéphane wrote: > I'm opening a task for network-manager to update its logic and instead only > call resolvconf if /etc/resolv.conf is a symlink to...
I don't see the need for NM ever to refrain from calling resolvconf. What's best is for everything always to call /sbin/resolvconf if it exists, so that resolvconf always has the best available information, whether or not that is currently directly visible in /etc/resolv.conf. Callers --- and also callees (hook scripts) --- can _additionally_ look at /etc/resolv.conf and take different actions based on its characteristics, if that's necessary. In Debian resolvconf 1.67, for example, the hook script /etc/resolvconf/update.d/libc looks at /etc/resolv.conf and refrains from running /etc/resolvconf/update- libc.d/* if the latter is not a symlink to the dynamic resolv.conf. Other resolver libraries might legitimately do something similar. I am not sure, however, what NetworkManager should do (additionally to calling resolvconf) if /etc/resolv.conf is not a standard symlink. Given that the admin may want to change the symlink or put a static file there, NM shouldn't simply overwrite the file. Is there actually any reason for NM to do anything additional? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012355 Title: /sbin/resolvconf shouldn't abort when /etc/resolv.conf is not a symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1012355/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
