[rhelv6-list] /etc/resolv.conf getting replaced?

Collins, Kevin [BEELINE] KCollins at chevron.com
Thu Nov 18 20:03:05 UTC 2010


Thanks, Justin!

The Migration Guide has this to say:

NetworkManager
Red Hat Enterprise Linux 6 uses NetworkManager by default when
configuring network interfaces.

Not much help... :(

I was under the impression that NetworkManager was replacing network -
did not even look for anything else. This sounds like the right way to
go.

Thanks,

Kevin

-----Original Message-----
From: Justin Clift [mailto:jclift at redhat.com] 
Sent: Thursday, November 18, 2010 10:49 AM
To: Collins, Kevin [BEELINE]
Cc: Glaser, David; rhelv6-list at redhat.com
Subject: Re: [rhelv6-list] /etc/resolv.conf getting replaced?

If it helps, one of the first things I do on systems is disable
NetworkManager, then re-enable the "known good", older "network"
service.

You need to change the physical network devices to no longer be under
NetworkManager control:

  /etc/sysconfig/network-scripts/ifcfg-eth0
    NM_CONTROLLED="yes"

  to

  NM_CONTROLLED="no"

Then:

  $ sudo chkconfig NetworkManager off
  $ sudo chkconfig network on

This will cause the server style, non-dynamic non-NetworkManager
configuration to be used from the next boot onwards.

So, if you actually want NetworkManager running, don't do this. :)

Regards and best wishes,

Justin Clift


On 19/11/2010, at 3:12 AM, Collins, Kevin [BEELINE] wrote:

> Thanks - I should have mentioned that I am using completely static
networking information.
>  
> [root at cpafisxc ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE="eth0"
> BOOTPROTO="static"
> DNS1="xxx.xxx.xxx.xxx"
> DNS2=" xxx.xxx.xxx.xxx "
> GATEWAY=" xxx.xxx.xxx.xxx "
> HWADDR="00:1C:C4:DD:24:08"
> IPADDR=" xxx.xxx.xxx.xxx "
> NETMASK="255.255.254.0"
> NM_CONTROLLED="yes"
> ONBOOT="yes"





More information about the rhelv6-list mailing list