Description of Problem: neat doesn't start if /etc/resolv.conf is absent. Its's bad behavior, because somebody may try to use neat to create missed /etc/resolv.conf Version-Release number of selected component (if applicable): redhat-config-network-1.1.5-1 How Reproducible: always Steps to Reproduce: 1. mv /etc/resolv.conf /etc/resolv.conf.badneat 2. start neat Actual Results: neat will show traceback output and fall down Expected Results: neat must start with proposition to create missed /etc/resolv.conf Additional Information: the same in 7.3
Created attachment 65465 [details] neat traceback
Fixed in CVS.
Fix confirmed with redhat-config-network-1.1.12-1.