Bug 68897 - neat doesn't start if /etc/resolv.conf is absent
neat doesn't start if /etc/resolv.conf is absent
Status: CLOSED RAWHIDE
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-network (Show other bugs)
limbo
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
:
Depends On:
Blocks: 67217
  Show dependency treegraph
 
Reported: 2002-07-15 15:58 EDT by Leonid Kanter
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-07-17 08:29:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
neat traceback (681 bytes, text/plain)
2002-07-15 16:03 EDT, Eugene Kanter
no flags Details

  None (edit)
Description Leonid Kanter 2002-07-15 15:58:23 EDT
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
Comment 1 Eugene Kanter 2002-07-15 16:03:36 EDT
Created attachment 65465 [details]
neat traceback
Comment 2 Trond Eivind Glomsrxd 2002-07-16 18:53:51 EDT
Fixed in CVS.
Comment 3 Jay Turner 2002-07-29 13:23:12 EDT
Fix confirmed with redhat-config-network-1.1.12-1.

Note You need to log in before you can comment on or make changes to this bug.