bug in resolv.conf rewrite
I may have found a bug in the resolv.conf rewriting code. Here is the scenario that caused this: 1) Booted up with wireless network, ISP #1. I didn't verify, but the file should have contained: nameserver A.B.C.35 nameserver A.B.C.36 2) Connected to physical ethernet, ISP #2. The contents of /etc/resolv.conf now has, with names obscured in CAPS # generated by NetworkManager, do not edit! DOMAIN.NAME.COMPANY.COM.search DOMAIN.NAME.COMPANY.COM. nameserver X.Y.26.118 nameserver X.Y.12.27 nameserver A.B.C.35 # NOTE: the glibc resolver does not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver A.B.C.36 The search line is broken. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: bug in resolv.conf rewrite
On Fri, Aug 15, 2008 at 4:55 PM, Miner, Jonathan W (US SSA) [EMAIL PROTECTED] wrote: I may have found a bug in the resolv.conf rewriting code. Here is the scenario that caused this: 1) Booted up with wireless network, ISP #1. I didn't verify, but the file should have contained: nameserver A.B.C.35 nameserver A.B.C.36 2) Connected to physical ethernet, ISP #2. The contents of /etc/resolv.conf now has, with names obscured in CAPS # generated by NetworkManager, do not edit! DOMAIN.NAME.COMPANY.COM.search DOMAIN.NAME.COMPANY.COM. nameserver X.Y.26.118 nameserver X.Y.12.27 nameserver A.B.C.35 # NOTE: the glibc resolver does not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver A.B.C.36 The search line is broken. Yes, I accidentally made a typo with that commit, but Dan fixed it on August 12th, r3943. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
RE: bug in resolv.conf rewrite
Thanks.. I hadn't svn updated in the last several days. -Original Message- From: Tambet Ingo [mailto:[EMAIL PROTECTED] Sent: Fri 8/15/2008 10:17 AM To: Miner, Jonathan W (US SSA) Cc: NetworkManager-list@gnome.org Subject:Re: bug in resolv.conf rewrite On Fri, Aug 15, 2008 at 4:55 PM, Miner, Jonathan W (US SSA) [EMAIL PROTECTED] wrote: I may have found a bug in the resolv.conf rewriting code. Here is the scenario that caused this: 1) Booted up with wireless network, ISP #1. I didn't verify, but the file should have contained: nameserver A.B.C.35 nameserver A.B.C.36 2) Connected to physical ethernet, ISP #2. The contents of /etc/resolv.conf now has, with names obscured in CAPS # generated by NetworkManager, do not edit! DOMAIN.NAME.COMPANY.COM.search DOMAIN.NAME.COMPANY.COM. nameserver X.Y.26.118 nameserver X.Y.12.27 nameserver A.B.C.35 # NOTE: the glibc resolver does not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver A.B.C.36 The search line is broken. Yes, I accidentally made a typo with that commit, but Dan fixed it on August 12th, r3943. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list