From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20020115 Description of problem: Whenever I bring up redhat-config-network and click Apply (even though I haven't changed anything), it will add 'PEERDNS=no' to /etc/sysconfig/network-scripts/ifcfg-eth0. For the corporate environment, this should not be the case. This is possibly related to the 'fix' for Bug #58110. Also when I click Apply, it asks if I want to change the file from chmod 600 to chmod 644. I click Yes, and the file has not changed permissions. If I click No, the file is then changed to chmod 644. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Click Apply in redhat-config-network Actual Results: 1. It adds 'PEERDNS=no' to /etc/sysconfig/network-scripts/ifcfg-eth0 2. It ask to change the permissions on the above file, and clicking Yes does nothing, while clicking No changed the permissions. Expected Results: The best result in #1 would probably be to add nothing to ifcfg-eth0. I understand that some ppp connections do not want PEERDNS=yes, but I certainly do not want PEERDNS=no. In #2, clicking Yes should change the file permissions, and clicking No should leave the permissions as they are. Additional info:
should be fixed in >0.9.22
Harald, I'm not seeing this package anywhere in the build system . . . am I missing something?
Fix confirmed with redhat-config-network-0.9.22-1.
*** Bug 62839 has been marked as a duplicate of this bug. ***