Bug 79107

Summary: ifup-post creates too many "search" lines in /etc/resolv.conf
Product: [Retired] Red Hat Linux Reporter: Jesse Thilo <redhat-com-box>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED RAWHIDE QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: medium    
Version: 8.0CC: rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-14 04:29:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Fix for multiple "search" line problem none

Description Jesse Thilo 2002-12-05 19:43:52 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
When ifup-post creates a new /etc/resolv.conf from the information in $DOMAIN,
$DNS1, and $DNS2, it writes a "search" line for every line in the original
/etc/resolv.conf, or two "search" lines if the original /etc/resolv.conf was
shorter than that.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. In /etc/sysconfig/network-scripts/ifcfg-eth0, add:
    PEERDNS="yes"
    DOMAIN="some.domain"
    DNS1="1.2.3.4"
    DNS2="5.6.7.8"
2. Run "ifdown eth0"
3. Run "ifup eth0"

Actual Results:  /etc/resolv.conf contained five "search some.domain" lines.

Expected Results:  /etc/resolv.conf should contain a single "search some.domain"
line.

Additional info:

Tested with a "BOOTPROTO=static" configuration only.
Comment 1 Jesse Thilo 2002-12-10 23:16:22 UTC 
Created attachment 88308 [details]
Fix for multiple "search" line problem
Comment 2 Bill Nottingham 2003-01-14 04:29:33 UTC 
Added in 7.03-1, thanks!