Precise now has bind9 1:9.8.1.dfsg.P1-4 so bug #920061 et al (re:
/etc/resolv.conf must be a symlink) may now have been fixed.
As I mentioned earlier (in #10), *this* report, #437783, originally
reported a distinct bug, namely that of postconf failing to open main.cf
and consequently
1:9.8.1.dfsg.P1-3 contains this fix but has not been synced to precise.
Might be a late candidate pre-final freeze - I'll try to catch LaMont to
discuss.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
I said:
Second, bind9 in Precise no longer defaults to registering 127.0.0.1 with
resolvconf on start
This is not quite correct. LaMont Jones wrote on 2012-02-17 in #933723
The next upload of bind9 will default to not enabling resolvconf but
this upload hasn't happened yet.
--
You received
** Also affects: postfix (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/437783
Title:
bind9 failed to start : resolvconf: Error:
The original problem was postconf failing to open main.cf and
/etc/resolvconf/update-libc.d/postfix trying to copy /etc/resolv.conf
onto itself at the line
cp /etc/resolv.conf $(/usr/sbin/postconf -h
queue_directory)/etc/resolv.conf
because postconf -h queue_directory returns a null string.
Now to address the bug which all the *duplicates*, except #511314 and
#437783, are about, namely, that installing bind9 aborts with
resolvconf: Error: /etc/resolv.conf must be a symlink.
First, resolvconf in Precise no longer returns an error condition if
/etc/resolv.conf is not a symlink, so the
This sounds like 933723 will fix it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/437783
Title:
bind9 failed to start : resolvconf: Error: /etc/resolv.conf must be a
symlink
To
With 19 people marking this as affecting them, and quite a few
duplicates, I think this is worthy of raising the importance to Medium.
** Changed in: bind9 (Ubuntu)
Importance: Low = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Summary changed:
- package bind9 1:9.6.1.dfsg.P1-3 [modified:
usr/share/bind9/bind9-default.md5sum] failed to install/upgrade: subprocess
installed post-installation script killed by signal (Interrupt)
+ bind9 failed to start : resolvconf: Error: /etc/resolv.conf must be a symlink
--
bind9
