Bug 130699 - dhclient nukes /etc/resolv.conf
Summary: dhclient nukes /etc/resolv.conf
Alias: None
Product: Fedora
Classification: Fedora
Component: dhcp   
(Show other bugs)
Version: rawhide
Hardware: i686 Linux
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-08-23 19:50 UTC by Zack Cerza
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: initscripts-7.67-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-23 20:05:01 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:566 normal SHIPPED_LIVE Updated dhcp and dhclient packages 2005-05-26 04:00:00 UTC

Description Zack Cerza 2004-08-23 19:50:20 UTC
Description of problem:
My /etc/resolv.conf was overwritten after a reboot with a single byte:
root@treefrog ~ =) # hexdump /etc/resolv.conf
0000000 000a                                   

Version-Release number of selected component (if applicable):
dhclient-3.0.1-7 (there's no dhclient component)

How reproducible:

Steps to Reproduce:
1. # service network stop
2. /etc/resolv.conf should still be fine.
3. # service network start
Actual results:
/etc/resolv.conf is overwritten with a single byte.

Expected results:
Normal operation.

Additional info:

Comment 1 Jason Vas Dias 2004-08-23 20:05:01 UTC
Yes, sorry - there was a typo in initscripts-7.66-1 - 
this is fixed in initscripts-7.67-1 .

Comment 2 John Flanagan 2004-12-21 19:41:48 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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