Re: resolv gets wacked after reboots

[Curtis Vaughan <curtis@npc-usa.com>]

In addition to what I've written already:
I noticed that in /etc/network/if-up.d there is a script  
000resolvconf and in /etc/network/if-down.d there is a script  
resolvconf. The latter looks like it clears the resolv.conf file,  
while the former sets it up. I changed the mode on these from 755 to  
644. Will this solve the problem? Unfortunately, I can't reboot  or  
do an ifup or ifdown right now to check that.

On 12 juil. 05, at 11:59, Curtis Vaughan wrote:

> On one Debian server (and only on one of several that we have - all  
> being sarge) after every reboot, the resolv.conf file is empty.
>
> The only thing different about this computer compared to the rest  
> is that the /etc/resolv.conf is a link to /etc/resolvconf/run/ 
> resolv.conf and I don't know why.
> The IP on all servers is static (set in /etc/network/interfaces).
> I have at times manually edited /etc/resolv.conf to have the set  
> nameservers I want it to have (removing the link). But when I  
> reboot, it is clear again. Same applies for manually editing /etc/ 
> resolvconf/run/resolv.conf. Although I manually edit it, after  
> rebooting it is clear.
>
> What is going on?
>
> Thanks.
>
> Curtis
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.orgwith a  
> subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org