This bug was fixed in the package resolvconf - 1.63ubuntu8
---------------
resolvconf (1.63ubuntu8) precise; urgency=low
* Use a post-stop script for disabling resolvconf, not a pre-stop script,
since upstart seems to be silently ignoring pre-stop when there's no
main process. LP: #933566.
* debian/postinst: mkdir -p /run/resolvconf/interface again, just in case
there's been a reboot between the preinst and postinst which would wipe
out /run. May or may not address LP 933035.
* debian/config, debian/templates, debian/postinst: if we don't know that
/etc/resolv.conf was being dynamically managed before install (in at
least some cases), link the original contents of /etc/resolv.conf to
/etc/resolvconf/resolv.conf.d/tail so that any statically configured
nameservers aren't lost. LP: #923685.
* when called with --enable-updates, ignore failures from the hooks.
LP: #933723.
-- Steve Langasek <steve.langa...@ubuntu.com> Mon, 20 Feb 2012 19:17:32 +0000
** Changed in: resolvconf (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933566
Title:
Stopping resolvconf doesn't disable updates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933566/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
