On Sun, 2008-08-10 at 23:10 -0400, Tom Lane wrote: > Dan Williams <dcbw@xxxxxxxxxx> writes: > > This is _exactly_ the problem that other distros use resolvconf for; > > stuff updates /etc/resolv.conf all the time, > > Uh, *what* stuff? I have never had such a problem before in any Fedora > version (or any other platform for that matter). VPNs (vpnc, ipsec, pptp, openvpn), PPP (for 3G cards, 56k dialup), ISDN, etc. Any time you have connections that may go up and down. > And before you dismiss the idea that NetworkManager is doing it, you > need to explain away the line "# generated by NetworkManager, do not edit!" > that's being inserted during the overwrite. The file got rewritten the last time you shut down and NM got stopped. Since all network interfaces got brought down, there were no valid DNS servers to use. Thus, you end up with an empty resolv.conf at shutdown time. When you next reboot, since you turned of NM, there is nothing to update resolv.conf, and thus you still don't have anything there. Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
