> On Jul 27, 2014, at 13:33, Grand Duet <grand.d...@gmail.com> wrote: > > 2014-07-27 12:29 GMT+03:00 Neil Bothwick <n...@digimed.co.uk>: >>> On Sun, 27 Jul 2014 12:21:23 +0300, Grand Duet wrote: >>> >>> In short: the contents of the file /etc/resolv.conf >>> is unpredictably different from one reboot to another. >>> It is either >>> # Generated by net-scripts for interface lo >>> domain mynetwork >> >> That's what you get when lo comes up. >> >>> or >>> # Generated by net-scripts for interface "eth0" >>> nameserver My.First.DNS-Server.IP >>> nameserver My.Second.DNS-Server.IP >>> nameserver 8.8.8.8 >> >> That's what replaces it when eth0 comes up. >> It looks like eth0 is not being brought up fully > > It sounds logical. But how can I fix it? > > Can carrier_timeout_eth0= setting in /etc/conf.d/net file help? > If so, how much seconds should I use? > >> what do your logs say? > > Could you, please, be more precise where to look for "logs". > >> It might be worth putting logger commands in preup(), >> postup() and failup() in conf.d/net. > > Currently, I have no such functions in my /etc/conf.d/net file. > Shall I copy them there from > /usr/share/doc/netifrc-0.2.2/net.example > > Could you, please, be more specific on these "logger commands" too. > >>> I tried to chmod this file to be unwrittable even for root >>> but after a reboot it have been overwritten anyway. >> >> You can't stop root overwriting a file, root laughs in the face of file >> permissions. >> >> BTW, I'm not sure if it's still relevant, but I don't think you ever >> posted the contents of /etc/resolvconf.conf, if it exists. > > I do not have such file. Of course, if you do not mean /etc/resolv.conf > But I have posted its content above. >
Depending on your filesystem a temporary solution to your problem is to setup /etc/resolv.conf correctly and then: chattr +i /etc/resolv.conf After that the content of the file will not change. -- -Matti
