On Tue, Jun 26, 2012 at 15:58:27 -0000, Thomas Hood wrote:
> 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.

Yes, exactly.  (I was just starting to compose a message
saying 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?

I'm not very familiar with the details of NM's operation,
but I gather the point of these exit-status checks, etc. was
to allow NM to continue to maintain /etc/resolv.conf
directly even when the resolvconf package was installed, by
deciding that resolvconf wasn't actually maintaining
/etc/resolv.conf.

Given resolvconf's current higher-profile status, though,
I'm not sure that use-case still applies.  I could see the
admin wanting to make /etc/resolv.conf a plain file he/she
controls manually, or wanting to leave it under the standard
control of resolvconf -- but I don't know if there's a
situation where NM needs to be directly managing a
plain-file /etc/resolv.conf itself any more.

(But if there is, it seems like it should be possible to
enable that behavior without disabling resolvconf updating.)

                                                Nathan

-- 
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

Reply via email to