Re: [gentoo-user] resolv.conf is different after every reboot

[Grand Duet]

2014-07-27 22:13 GMT+03:00 Neil Bothwick <neil@××××××××××.uk>:
> On Sun, 27 Jul 2014 13:33:47 +0300, Grand Duet wrote:
>
>> > 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?
>
> By identifying how far it is getting and why no further.
> But it appears that eth0 is being brought up correctly
> and then the config is overwritten by the lo config.

I think so.

As I have already reported in another reply to this thread,
it is my first reboot after commenting out the line
     dns_domain_lo="mynetwork"
and so far it went good.

Moreover, the file /etc/resolv.conf has not been overwritten.

I still have to check if everything else works fine and
if I will get the same result on the next reboot
but I hope that the problem has been solved.

But it looks like a bug in the net csript.
Why lo configuration should overwrite eth0 configuration at all?

> I'd suggest going with the suggestion of disabling hotplugging for net.* interfaces.

Thank you for the advice, I will try this if it appears that the
problem has not been solved yet.

>> > what do your logs say?
>>
>> Could you, please, be more precise where to look for "logs".
>
> /var/log/messages, dmesg, the standard places.
>
>> > 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
>
> Yes, they are run are various stages of bringing up the interface.
>
>> Could you, please, be more specific on these "logger commands" too.
>
> I meant to add a logger call to each function to see how far it gets
>
> logger "eth0 going up"
> logger "eth0 up"
> logger "eth0 failed"
>
> or something like that. but it appears this is moot and eth0 is up
> successfully.

Thank you for this explanation as well. I will try it a bit later
but I feel that before doing it I should refresh my knowledge
of scripts in general.

>> > 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.
>
> I meant /etc/resolvconf.conf, which you were asked for before, but as
> you don't have it, the problem isn't there.
>
>
> --
> Neil Bothwick
>
> Vital papers will demonstrate their vitality by moving to where you
> can't find them.