[rhelv6-list] dhclient running TWICE during boot (RHEL 6.2)

[Manuel Wolfshant]

On 04/30/2012 03:44 PM, "Weiergräber, Oliver H." wrote:
> Are you sure "chkconfig network off" has been run so NetworkManager owns the network configuration?  It almost sounds like both "network" and "NetworkManager" are chkconfig'd on.
>
> For reasons I do not understand, this is exactly the default in RHEL 6 - network connections is jointly managed by network and NetworkManager.
> I have also seen strange behavior under certain conditions which was immediately rectified by turning one of the two services off!
> IMHO users should be urged to decide which one to use - running both seems to work most of the time, but is prone to errors...
Both services can coexist but NetworkManager must be told to not handle 
the interfaces which are managed by the network service ( via the 
NM_CONTROLLED parameter )
Closest think resembling to docs that I could find is 
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Deployment_Guide/s2-networkscripts-interfaces_network-bridge.html 
but the parameter is there since Fedora 9 or 10.

     manuel



>> On Sun, 2012-04-29 at 22:43 -0700, thomas at redhat.com wrote:
>>>> Can anyone explain how this is supposed to work and where I've gone
>>>> wrong?  Do other people see duplicated lease files for the same
>>>> interface when using DHCP?
>>> What does /etc/sysconfig/network-scripts/ifcfg-eth0 look like? I
>>> generally set ONBOOT=no if I'm going to let NM manage the interface.
>>> What happens if you set ONBOOT=no and NM_CONTROLLED=yes? Do you still
>>> see the two dhclient processes?
>> It's ifcfg-Auto_eth0 actually, since it was created by NM.  And it has
>> ONBOOT=yes.  It looks like this:
>>
>>         HWADDR=05:35:45:D5:F5:35
>>         TYPE=Ethernet
>>         BOOTPROTO=dhcp
>>         DEFROUTE=yes
>>         PEERROUTES=yes
>>         IPV4_FAILURE_FATAL=yes
>>         IPV6INIT=no
>>         NAME="Auto eth3"
>>         UUID=75a5eeaf-c5b8-45af-b5e9-e95589be7a35
>>         ONBOOT=yes
>>         DHCP_HOSTNAME=myhost
>>
>> I was assuming that if ONBOOT was not set properly, then the interface
>> would not come up at boot time.  But maybe NetworkManager doesn't pay
>> attention to that value?  If so why is it there (note the above file was
>> created by NetworkManager, not by me).
>>
>> I've never heard of NM_CONTROLLED before; is this documented somewhere?
>> I didn't see it in the docs.  Looking through what the scripts do, it
>> doesn't seem to me that this variable has much use.  It seems to set
>> USE_NM to true, but that's only used (as far as I can tell) to set the
>> UUID variable if we don't have one... which we do (see above).
>>