Comment 31 for bug 448095

I think the problem is that there is a significant post-boot delay before
resolv.conf is updated. It took ~ 90sec (after gdm start) on last boot.
But at least it's working

+Reardon

On Mon, Dec 28, 2009 at 5:11 AM, Sander van Grieken <sander@3v8.net> wrote:

> ok, time for a full checklist :)
>
> - update /sbin/resolvconf from bug attachment
> - update /etc/resolvconf/update.d/libc from bug attachment
> - install /etc/init/resolvconf.conf from bug attachment
> - remove /etc/rcS.d/S07resolvconf
> - make sure /etc/resolv.conf symlinks to
> /lib/init/rw/resolvconf/resolv.conf
>
> vpn or tunnelling should work as good as before. Nothing has changed for
> 'late' connections.
>
> debugging is a bit hard, but you can see the non-zero exit code if you
> boot in rescue mode.
>
> --
> resolvconf starts after ifupdown, does not pick the dns-nameserver and
> dns-search lines up from /etc/network/interfaces
> https://bugs.launchpad.net/bugs/448095
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ifupdown” package in Ubuntu: Won't Fix
> Status in “resolvconf” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: resolvconf
>
> ifdown -a ; ifup -a fixes the problem after a reboot.
>
> ProblemType: Bug
> Architecture: i386
> Date: Sat Oct 10 17:55:06 2009
> DistroRelease: Ubuntu 9.10
> Package: resolvconf 1.44ubuntu1
> PackageArchitecture: all
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
> SourcePackage: resolvconf
> Uname: Linux 2.6.31-13-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/448095/+subscribe
>
>