I'm seeing this issue from a clean Ubuntu precise amd64 AMI
(http://cloud.ubuntu.com/ami/).
With nothing but vpnc installed, I did some of the following:
ubuntu@ip-10-116-125-233:~$ sudo vpnc myvpnc.conf
sudo vpnc myvpn.conf
resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing
Here's some information:
ubuntu@ip-10-116-125-233:~$ ls -l /etc/resolv.conf
-r--r--r-- 1 root root 63 May 29 13:42 /etc/resolv.conf
ubuntu@ip-10-116-125-233:~$ lsattr /etc/resolv.conf
-e- /etc/resolv.conf
ubuntu@ip-10-116-125-233:~$ ls -l /run/resolvconf
total 0
drwxr-xr-x 2 root root
Louis Li: Your problem looks like bug #1003842, not this one. Please
follow up at #1003842.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1003842
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(Argh. That should have been #1000244, not #1003842.)
Louis Li: Your problem looks like bug #1000244, not this one. Please
follow up at #1000244.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1000244.
--
You received this bug notification because you are a member of Ubuntu
Unfortunately, the side effect of this fix is that now resolv.conf is
never updated by NM, causing anyone who upgraded to 12.04 to have broken
DNS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922677
Cerin: Can you please elaborate? On a properly configured system NM and
resolvconf work together correctly. If name resolution is not working
on your system then let's find out why.
Please send the output of:
ls -l /etc/resolv.conf
lsattr /etc/resolv.conf
ls -l /run/resolvconf
I need this package in Oneiric, and have installed the (precise) deb
manually. ..is it possible to release this newer version for oneiric?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922677
Title:
On Fri, Jan 27, 2012 at 22:04, Steve Langasek steve.langa...@canonical.com
wrote:
Making files immutable is absolutely the wrong way to go.
Agreed.
I think the long term correct solution would be
to drop the debconf question altogether and
adjust the package to only linkify on initial
On Sat, Jan 28, 2012 at 12:49:32PM -, Thomas Hood wrote:
I think the long term correct solution would be
to drop the debconf question altogether and
adjust the package to only linkify on initial install,
You mean that the postinst refrains from linkifying if the argument of
configure
This bug was fixed in the package resolvconf - 1.63ubuntu4
---
resolvconf (1.63ubuntu4) precise; urgency=low
* dhclient hook: Only trigger if /etc/resolv.conf is a symlink.
* postinst: Set resolvconf/linkify-resolvconf to false after initial
conversion, ensuring upgrades
* dhclient hook: Only trigger if /etc/resolv.conf is a symlink.
* Make resolvconf exit 0 when /etc/resolv.conf isn't a symlink
In the Debian version of resolvconf, interface-configurer hook scripts always
run /sbin/resolvconf if it's present, whether or not /etc/resolv.conf is a
symlink.
* postinst: Set resolvconf/linkify-resolvconf to false after initial
Is this (i.e., maintainer scripts changing the answers to debconf
questions) a recommended practice?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yeah, I later discovered that changing to exit 0 will break resolv.conf with
Network Manager.
Matt Trudel is aware of it and the Network Manager code will be changed to a
logic similar to that of the dhclient hook (check for resolvconf and for
/etc/resolv.conf being a symlink).
As for the
So what rule is Ubuntu adopting which suppliers of nameserver
information are supposed to follow?
In Debian the rule is: If /sbin/resolvconf is present then send the
information to /sbin/resolvconf (regardless of whether or not
/etc/resolv.conf is a symlink).
Is Ubuntu's rule the following? If
As for the debconf change, that was on the
recommendation of Steve, so I assume that's
fine. Maybe not the recommended way but
certainly not the worst way of doing it either :)
I worry that doing this violates the principle that debconf is not a registry.
Debconf is a way for the
Yeah, currently Ubuntu's rule is /sbin/resolvconf exists and
/etc/resolv.conf is a symlink. We don't really check where the symlink
points to even though I guess we should :)
We made resolvconf a hard depend of ubuntu-minimal which means it gets
on any system we can call an Ubuntu system and is
Thomas,
Making files immutable is absolutely the wrong way to go. In chatting
with Stéphane about this bug, I think the long term correct solution
would be to drop the debconf question altogether and adjust the package
to only linkify on initial install, but that's a change I wanted to talk
with
17 matches
Mail list logo
