Hi Stéphane.
It was once the case that NM relied on resolvconf's exit status to tell
it what it should do next, but in Precise the status was changed to 0,
so there is no way that NM can still be using the status to make
decisions.
[ -L /etc/resolv.conf ] || { report_err "/etc/resolv.conf isn't a
symlink, not doing anything."; exit 0; }
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012355
Title:
/sbin/resolvconf shouldn't abort when /etc/resolv.conf is not a
symlink
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1012355/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
