Bug 151808 - presence of HWADDR= in ifcfg-ethX cause dhclient run twice
Summary: presence of HWADDR= in ifcfg-ethX cause dhclient run twice
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-22 16:12 UTC by Martin (calim)
Modified: 2014-03-17 02:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-09-21 21:10:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin (calim) 2005-03-22 16:12:51 UTC
Description of problem:

presence of HWADDR= in ifcfg-ethX cause dhclient runs two time on this interface.

How reproducible:

full reproductible.

Steps to Reproduce:
1. make sure you have only one NIC configured in /etc/sysconfig/network-script
( for example ifcfg-eth0 ), with ONBOOT=yes and BOOTPROTO=dhcp. It's to be sure
that DHCP will not be used by another NIC of your server.

2. add HWADDR=<your MAC addr> to this file.
3. reboot your server.
4. There are two dhclient's running process.

  
Actual results:

Two dhclient running processes, on the same interface

1856 ?        Ss     0:00 /sbin/dhclient -1 -q -lf
/var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid eth0
 2447 ?        S<s    0:00 /sbin/dhclient -1 -q -lf
/var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid eth0

Expected results:

One dhclient process by interface.

Additional info:
If you comment the concerned line HWADDR= with a "#", you'll
find two dhclient running processes too !

Comment 1 Martin (calim) 2005-03-22 16:15:30 UTC
Here it is by deduction the workaround :

1. Remove the line which contain HWADDR= in ifcfg-eth0
2. reboot your server
3. There is only one dhclient running.

Comment 2 Bill Nottingham 2005-03-23 04:09:58 UTC
This is likely fixed with hotplug-2002_04_1-20.4, which should be in the beta
channel for the next update soon.


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