Re: /etc/resolv.conf being blanked

[tomas@tuxteam.de]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Oct 11, 2015 at 12:23:03PM +0100, Dominic Hargreaves wrote:
> On Sun, Oct 11, 2015 at 12:39:02PM +0200, tomas@tuxteam.de wrote:
> > On Sun, Oct 11, 2015 at 12:05:53PM +0100, Dominic Hargreaves wrote:
> > > [Please CC me on replies]
> > > 
> > > Hi,
> > > 
> > > On my freshly installed Debian jessie system, running XFCE and
> > > Network Manager, I'm seeing /etc/resolv.conf being blanked every so
> > > often (it seems to be about every 20 minutes). I can't see what is doing
> > > this; there's nothing in the system logs which correlates with this event.
> > 
> > See my other post: the brutal (but effective) self-defense tool I used
> > (back then, when NM was yet allowed on my boxes ;-) was to "chattr +i"
> > the file. With some luck I'd find complaints in the log files which helped
> > clear up which program (and in which context) was trying to do something
> > to the files.
> > 
> > The nice part of chattr is that it protects the direntry too (so the
> > obvious fall-back of removing and re-creating doesn't help).
> 
> But I *want* NM to update the file, and I don't have any evidence that
> it's NM blanking it here. So preventing updates isn't what I want.
> 
> Having said that, you're right that looking for complaints could be
> an effective debugging tool. I'll give that a go.

Yes, that was my primary aim too :-)

Some day those i-do-everything-and-i-know-better-than-you programs will
learn about chattr. Then we're hosed; so please you do it very quietly
and don't tell anybody ;-D

> I did just notice that there is a third state that the file sometimes
> ends up in, as well as the expected one which begins "Generated by
> Network Manager". This is a file which just contains one nameserver
> entry containing the IPv6 resolver. Odd.

Indeed.

regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlYaP8QACgkQBcgs9XrR2kbrGACeP0iySkaeEXhIuqiycM5kheVP
PHYAnj/fK1zD43PuYWSN8leV8jEUWa1t
=b0Yg
-----END PGP SIGNATURE-----