Web lists-archives.com

Re: Why does resolv.conf keep changing?

On Thu, Oct 26, 2017 at 12:24:32PM +0100, Darac Marjal wrote:
> Actually, there's no need to duplicate the effort. As I understand it,
> resolvconf is basically an optional helper program. Software that
> automatically modifies /etc/resolv.conf should first test for the presence
> of resolvconf (whether that be checking for the configuration directory of
> resolvconf or checking that resolvconf is running or... however resolvconf
> desires to be detected). If resolvconf is available, the changes are
> co-ordinated through resolvconf, otherwise, /etc/resolv.conf is modified
> directly.
In my case resolvconf is not installed/available and I want resolv.conf
to be left alone.  I want any other package that thinks it needs to
modify resolv.conf to leave it along.  I also think that would be useful
in the case where resolvconf gets unexpected installed later.  That is
not a specific concern for me, but in a situation where multiple
administrators are involved with managing a system it could happen.

Based on your proposal the situation which I have would not be
addressed.  I am specifically saying that there should be a way to mark
resolv.conf as static so that any package that touches it can check for
that directive.  There is no need for packages to coordinate between
themselves in that case.  They need only to check for the marker in
resolv.conf and if it is there (indicating that it should not be
modified) then they simply discontinue processing.

> The problem is that I don't think that resolvconf can require packages to
> use it. This is similar to other higher-level APIs such as pulseaudio. If
> the software knows to use pulseaudio, then it can get mixed, rerouted etc by
> pulseaudio, but it's difficult to mandate that software stop sending audio
> directly to /dev/dsp (well, unless you're a distribution which applies
> patches to upstream software in order to harmonize the experience of its
> users).

I can see the utility of resolvconf and in packages coordinating their
modifications of resolv.conf.  However, I still maintain that there
should be a simple way for the admin to mark resolv.conf in such a way
that no package will modify it.  This should be possible without
resorting to hacks like making resolv.conf immutable.



Roberto C. Sánchez