Comment 3 for bug 871058

Hi Clint,

OK, but it is common for /etc/resolv.conf not to be a symlick to
/etc/resolvconf/run/resolv.conf.

On the first apt-get run to install bind9, it halted at configuring
bind9 and I had to kill it after waiting many minutes.

I've seen this failure many years ago and it is still there. Should
the file not being a symlink really flummox the perl program that
configures bind9?

I waited a long time before having to use the kill command.

Thanks!
Mike

On Sat, Oct 8, 2011 at 19:35, Clint Byrum <email address hidden> wrote:
> * Stopping domain name service... bind9        [168G resolvconf: Error:
> /etc/resolv.conf must be a symlink
>
> This is actually a problem with the way resolvconf handles bind9, not
> bind9 directly.
>
> ** Package changed: bind9 (Ubuntu) => resolvconf (Ubuntu)
>
> ** Changed in: resolvconf (Ubuntu)
>   Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/871058
>
> Title:
>  package bind9 1:9.7.3.dfsg-1ubuntu2.2 failed to install/upgrade:
>  subprocess installed post-installation script returned error exit
>  status 1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/871058/+subscriptions
>