Debian BTS wrote:
> The interface is not started automatically at boot, I start it after
> boot with an 'ifup eth0' as root.
> Then resolvconf should automatically add the two nameservers to
> /etc/resolv.conf, that is a symlink pointing to
> /etc/resolvconf/run/resolv.conf
> but this isn't happening and I have /etc/resolv.conf empty.
> I am forced to use 'cat /etc/resolvconf-eth0 | resolvconf -a eth0',
> where resolvconf-eth0 is file in which I have written the ip of the two
> nameservers above, to have resolv.conf correctly set up.
Make sure that the logical interface definition being applied to eth0
contains one and only one "dns-nameservers" option line where the
option keyword is followed by the required nameserver addresses
separated by spaces.
Make sure that /etc/network/if-up.d/000resolvconf is present and has
execute permission.
Make sure that /etc/resolv.conf points to
"/etc/resolvconf/run/resolv.conf".
Make sure that /etc/resolvconf/run points to "/dev/shm/resolvconf".
Make sure that there the /dev/shm/ filesystem is not full. Do "df"
and look at the Use% for /dev/shm.
Make sure that /dev/shm/resolvconf/ exists.
Make sure that root can create files in /dev/shm/resolvconf/.
Make sure that /dev/shm/resolvconf/interface/ exists.
If all of the above checks out then we need to start debugging.
Please add
LOG=/tmp/resolvconf.log
echo "-------------" >> $LOG
echo "ARGS: $*" >> $LOG
echo "run:" >> $LOG
ls -dl /etc/resolvconf/run/* >> $LOG
echo "interface:" >> $LOG
ls -l /etc/resolvconf/run/interface >> $LOG
echo "-------------" >> $LOG
to the top of it and send the contents of /tmp/resolvconf.log after a
reboot.
--
Thomas Hood
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
