Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 76681

Summary: Location of iface-specific dhclient files
Product: [Retired] Red Hat Linux Reporter: Dan Morrill <morrildl>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED WONTFIX QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: rvokal
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-29 20:21:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dan Morrill 2002-10-24 21:28:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

Description of problem:
/etc/sysconfig/network-scripts/ifup is responsible for invoking dhclient
where/when appropriate.  When run, ifup invokes dhclient to use a config file
specific to that device; this is fine, though it may be a matter of taste.

However, the config files are /etc/dhclient-${IFACE}.conf -- e.g.
/etc/dhclient-eth0.conf.  This is Ugly(TM) (IMO.)

These config files should go in either /etc/sysconfig/network-scripts, or at
least in a new /etc/dhclient.d/ or something.  (I personally favor
/etc/dhclient.d/, but whatever.)

Note that this is a style/consistency thing, not a true bug (since ifup does
work as-is.)  This may be related to bug 74862.

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

How reproducible:

Steps to Reproduce:
1. Boot up w/ DHCP enabled.

Actual Results:  dhclient looks for iface-specific config data in

Expected Results:  dhclient should look for iface-specific config data in
something like /etc/dhclient.d/dhclient-${IFACE}.conf

Additional info:

Comment 1 Bill Nottingham 2005-09-29 20:21:00 UTC
Closing bugs on older, no longer supported, releases. Apologies for any lack of

At this point, I doubt that this will change, it doesn't seem to be worth the