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

[Paul Smith]

On Mon, 2012-04-30 at 13:07 +0000, Brian Long (brilong) wrote:
> If you want to leave network and NetworkManager enabled on boot, you
> could set "ONBOOT=no" in your ifcfg-Auth-eth0 file.  I believe ONBOOT
> is only used by the network service and "NM_CONTROLLED" is used by
> NetworkManager.  I'm fairly certain that if ONBOOT=no, NetworkManager
> will still try to enable the interface depending on the GUI settings.

Man this is ... weak.

So I tried this.  If I set ONBOOT=no and NM_CONTROLLED=yes, then the
system boots BUT it never brings up the network interface at all, until
I log in at the console.  That's not acceptable, I want the network
interface to come up automatically at boot so I can access it remotely
if it reboots without having to go log into it.

So I switched them and set ONBOOT=yes and NM_CONTROLLED=no.  When I
rebooted this time the network interface came up (with the "wrong" IP
address), but no default route was created!  So I couldn't access any
other hosts.  Of course I can do this by hand but again, I don't want to
have to to fix the host whenever it reboots.

So I set ONBOOT=yes again and removed the NM_CONTROLLED variable and it
went back to the old behavior... still broken but at least I can access
the system by IP address!


Here's even more awesome: looking through the scripts I saw a USE_NM
variable, so I tried adding "USE_NM=yes" to my ifcfg-Auto_eth0 script.
When I rebooted this time the boot process HUNG when S10network was
trying to bring up eth0.  I couldn't ^C or ^Z or switch to an alternate
console (maybe it's too early for them?).  The only keys that would do
anything were CTRL-ALT-DEL and that just brought me right back to the
same state.  Trying to boot into safe mode gave me a kernel panic.

Eventually I had to boot off of a separate DVD, mount the partition,
remove that line, then I could boot again.  Fun!