The patch I submitted in #23 fixes the bug insofar as it changes
resolvconf's pppd hook script so that it doesn't create an unneeded
"ppp0" record when pppd has been run by nm-pptp-service. However, it
has the shortcoming that the hook script fails to delete such a record
created by an earlier version of the script. The result is that if
resolvconf is upgraded while pppd is running under nm-pptp-service then
the unwanted record remains in the database even after the PPP interface
has been brought down. Not good. The problem disappears on reboot, but
still.
The attached patch (skip-resolvconf-under-pptp_20120618th1.diff) fixes
this. Patched with this patch instead of the previous one, the hook
script creates the record with a different name (e.g., 'ppp0.pppd') from
the name used before ('ppp0') and, on down, unconditionally deletes the
old record.
The new name follows conventions whereas the old name did not, so the
name change is in itself an improvement.
(The name change will also be made in Debian eventually. I'm not sure
about the special casing of nm-pptp-service yet ---- I will have to look
at Debian's n-m.)
** Patch added: "Patch to fix resolvconf's pppd hook scripts such that they
don't call resolvconf if pppd was called by nm-pptp-service"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/994575/+attachment/3194149/+files/skip-resolvconf-under-pptp_20120618th1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994575
Title:
/etc/ppp/ip-up.d/000resolvconf should "exit 0" if pppd was run by NM,
since NM will register the nameserver addresses itself
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/994575/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
