On Sun, Jan 23, 2011 at 9:30 AM, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote:
> On Sun, Jan 23, 2011 at 2:46 AM, Tom H <tomh0665@xxxxxxxxx> wrote:
>> On Sat, Jan 22, 2011 at 11:28 PM, Nico Kadel-Garcia <nkadel@xxxxxxxxx> wrote:
>
>>> The key to *keeping* it off in RHEL 6, and I assume in CentOS 6, is
>>> the setting NM_CONTROLLED="no" in the
>>> /etc/sysconfig/network-scripts/ifcfg-* files. This is a new setting in
>>> RHEL 6, and I'm having difficulty finding documentation for it, but it
>>> seems to work in keeping NetworkManager's greedy little paws off my
>>> stable settings.
>>
>> In both the RH and FP docs, the only reference that I've found is in
>> this section:
>> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/sect-Virtualization-Network_Configuration-Bridged_networking_with_libvirt.html
>
> Yeah, "libvirt" is not your friend for network configurations, nor is
> the "bridged" network setup used for KVM. It's not well supported,
> especially in the documentation.
>
>> RHEL 5 has a similar section so it's not a new setting, just a
>> not-well-documented one (like a DNS or DHCP one that you referred to
>> recently).
>
> libvirt is also not your friend for correct documentation. This *will
> not work* for RHEL 5 or CentOS 5, because there is nothing in the
> actual /etc/sysconfig/network-scripts to support it. You have to
> disable NetworkManager with chkconfig or rip it out, which is actually
> safer.
I was just pointing out the only section of RH documentation where
NM_CONTROLLED is mentioned. :)
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
