Description of problem: If /etc/resolv.conf is changed while dhclient is running (with PEERDNS=yes), /etc/resolv.conf get's overwritten even if PEERDNS was set to "no" befor it was shutdown. How reproducible: Always Steps to Reproduce: See bug #822930 Actual results: /etc/resolv.conf is empty (or contains previous data) Expected results: /etc/resolv.conf is not touched Additional info: This is just a problem if dhclient started with PEERDNS=yes and quits with PEERDNS=no (so the user expects dhclient no to touch resolv.conf)
(In reply to bug #822930, comment #7) > The network is configured using DHCP, dhclient creates a copy of the > original (a) /etc/resolv.conf in e.g. (b) > /var/lib/dhclient/resolv.conf.predhclient.breth0 . > When dhclient is shut down, it overwrites /etc/resolv.conf with (b), thus, > any changes that happened during the lifetime of dhclient to > /etc/resolv.conf are lost. I already removed this /etc/resolv.conf backup&restore part of dhclient-script in F-17: http://pkgs.fedoraproject.org/gitweb/?p=dhcp.git;a=commitdiff;h=1e3f54a9ec3e1610b8ad4920c6c6b0c4c80a1e22 I'm closing as fixed in rawhide. Feel free to reopen if you need to have this fixed in F-16.