Paul Smith ([email protected]) said: > 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.
NM honors ONBOOT=no, so this is expected. > 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. This means that it's only brought up by /etc/init.d/network; route should be grabbed from the DHCP server. > 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. USE_NM is internal initscripts accounting - I suppose it should be namespaced off. It's not ment as an end-user configuration variable. Bill _______________________________________________ rhelv6-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv6-list
