Re: why does resolv.conf change?
-----BEGIN PGP SIGNED MESSAGE-----
James Zuelow wrote:
>> Yet, relying on the immutability of /etc/resolv/conf is like
>> relying on
>> the persistence of files on /tmp: just DON'T!
> 2nd note that my suggestion to make /etc/resolv.conf immutable was not to keep his changes, but to cause the application making the changes to complain in the event log. Then the OP could fix or configure the offending application.
He probably realized that. He is criticizing not you but me for wanting
resolv.conf to stay the same.
BTW, your suggestion did not work for me:
# chattr +i /etc/resolv.conf
chattr: Operation not supported while reading flags on /etc/resolv.conf
Anyway, having reinstalled resolvconf, I know exactly what is modifying
resolv.conf now, namely resolvconf (and possibly others, but resolvconf
overrides those). While unable to stop the modifications, I noticed that
I can put my stuff in /etc/resolvconf/resolv.conf.d/head and it will
then still be there after resolvconf runs. It does not keep the unwanted
provider nameserver out of resolv.conf, but prepends it with
sufficiently many (3 suffices?) good nameservers, so it never gets used
and everything is fine. Problem solved.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----