[Resolvconf-devel] Bug#651801: Bug#651801: resolvconf: /etc/resolv.conf is a broken link after reboot

[Teodor MICU]

Hi,

2011/12/12 Thomas Hood <jdthood at gmail.com>:
> It is possible that this is the same issue as #651827.  The issue there is
> that no update is run at boot, so if your system only uses the base file
> (and no interface configurers, e.g., ifupdown, dhclient, are run) then your
> dynamically generated /etc/resolv.conf will be absent.

Well, I use resolvconf on all workstations in combination with
NetworkManager, dnsmasq and no entries in /etc/network/interfaces
except the 'lo' interface. On some of them I have some static DNS
entries (due to some bug when resolv.conf has no entries) and on all I
have a static list of domains to search.

Thus, I expect resolvconf to work with no entries on /e/n/i just fine.

> If you think that this may be the same issue, please test the patch I
> supplied in #651827, or do the following:
>
> In the "start" part of the case statement in the resolvconf init script,
> insert a
>
>     resolvconf -u

With this change the problem is fixed. This was the command I executed
manually to make it work after each reboot. Without this, the content
of /run/resolvconf is just one directory.

Thanks


------
/run/resolvconf:
total 0
drwxr-xr-x 3 root root  60 Dec 13 11:38 .
drwxr-xr-x 9 root root 220 Dec 13 11:38 ..
drwxr-xr-x 2 root root  40 Dec 13 11:38 interface

/run/resolvconf/interface:
total 0
drwxr-xr-x 2 root root 40 Dec 13 11:38 .
drwxr-xr-x 3 root root 60 Dec 13 11:38 ..