Re: resolv gets wacked after reboots

2005-07-13 Thread Thomas Hood
Package: resolvconf Version: 1.29 Severity: important 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

Re: resolv gets wacked after reboots

2005-07-12 Thread John Hasler
Bob Proulx writes: > If so then it needs to be purged to remove the configuration files. However, if it left behind scripts that are being executed at boot it is buggy. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTEC

Re: resolv gets wacked after reboots

2005-07-12 Thread Bob Proulx
Curtis Vaughan wrote: > John Hasler wrote: > >Remove the resolvconf package and make sure the link is removed as > >well. > > Resolvconf is not installed. Maybe it was at one time though. Perhaps it has left configuration files behind. dpkg -l resolvconf Does it say 'rc' as status? dpkg

Re: resolv gets wacked after reboots

2005-07-12 Thread John Hasler
Curtis Vaughan wrote: > 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. Those scripts are part of the resolvconf package. Remov

Re: resolv gets wacked after reboots

2005-07-12 Thread Curtis Vaughan
On 12 juil. 05, at 12:18, John Hasler wrote: 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

Re: resolv gets wacked after reboots

2005-07-12 Thread Thomas Hood
On Tue, 12 Jul 2005 11:59:37 -0700, Curtis Vaughan wrote: > What is going on? 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.) -- Thoma

Re: resolv gets wacked after reboots

2005-07-12 Thread John Hasler
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. -- John Hasler -- To UNSUBSCR

Re: resolv gets wacked after reboots

2005-07-12 Thread Curtis Vaughan
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

resolv gets wacked after reboots

2005-07-12 Thread Curtis Vaughan
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 wh