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-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
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-us...@lists.debian.orgwith a
Remove the resolvconf package and make sure the link is removed as well.
--
John Hasler
You have the resolvconf package installed and haven't set it up.
Either remove the package or read /usr/share/doc/resolvconf/README.gz.
(You probably need "dns-nameservers" options in /etc/network/interfaces.)
--
Thomas Hood
> Curtis Vaughan writes:
>
>> 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.
>>
>
> Remove the resolvconf package and make sure the link is removed as
> well.
> --
Resolvconf is not installed. Maybe it was at one time though.
Those scripts are part of the resolvconf package. Remove it. If it is not
installed remove the scripts (and the link) and try figure out what went
wrong so that you can file a bug.
--
John Hasler
Perhaps it has left configuration files behind.
dpkg -l resolvconf
Does it say 'rc' as status?
dpkg --status resolvconf | grep Status:
If so then it needs to be purged to remove the configuration files.
dpkg --purge resolvconf
Bob
However, if it left behind scripts that are being executed at boot it is
buggy.
--
John Hasler
Yes, there is a bug in resolvconf's removal logic. The problem
is that /etc/resolvconf/run/resolv.conf resides on a volatile
filesystem and is therefore empty after boot until something
writes to it. If the resolvconf package is removed then the
resolvconf program no longer updates the file. But the symlink
/etc/resolv.conf -> /etc/resolvconf/run/resolv.conf is only
deleted if the resolvconf package is _purged_.
Purging resolvconf should fix the user's problem.
The resolvconf package should be changed so that the symlink
is deleted on package removal.
--
Thomas Hood