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 anything. VPNC started in background (pid: 12101)... (but it's not actually connected) Upgrading resolvconf package: Unpacking replacement resolvconf ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up resolvconf (1.63ubuntu14) ... Processing triggers for resolvconf ... resolvconf: Error: /etc/resolv.conf isn't a symlink, not doing anything. -- 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: resolvconf should only convert /etc/resolv.conf to a symlink at initial installation time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/922677/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
