Bug 79107 - ifup-post creates too many "search" lines in /etc/resolv.conf
ifup-post creates too many "search" lines in /etc/resolv.conf
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
8.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-05 14:43 EST by Jesse Thilo
Modified: 2014-03-16 22:32 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-01-13 23:29:33 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Fix for multiple "search" line problem (463 bytes, patch)
2002-12-10 18:16 EST, Jesse Thilo
no flags Details | Diff

  None (edit)
Description Jesse Thilo 2002-12-05 14:43:52 EST
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 18:16:22 EST
Created attachment 88308 [details]
Fix for multiple "search" line problem
Comment 2 Bill Nottingham 2003-01-13 23:29:33 EST
Added in 7.03-1, thanks!

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