SCIENTIFIC-LINUX-USERS Archives

April 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Robert E. Blair" <[log in to unmask]>
Reply To:
Robert E. Blair
Date:
Fri, 8 Apr 2011 13:20:48 -0500
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (2579 bytes) , reb.vcf (446 bytes) , smime.p7s (6 kB)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I installed a server with the "workstation" configuration and simply
"rpm -e'ed" NetworkManager.  The result was just fine.  The old network
configuration layer is still underneath - the gui is gone though - but
who used that.

Nico Kadel-Garcia wrote:
| On Wed, Apr 6, 2011 at 2:50 AM, Ahmed El Zein
<[log in to unmask]> wrote:
|
|> I am looking at the logs and the only network related log that coincides
|> with the resolv.conf file changing is:
|> <29> Arp 6 06:40:49 NetworkManager[542]:    ifcfg-rh:
|> updating /etc/sysconfig/network-scripts/ifcfg-eth0
|>
|> at that point /etc/sysconfig/network-scripts/ifcfg-eth0 changes and gets
|> an NM_CONTROLLED="yes" added to it and the /etc/resolv.conf file is
|> replaced with the single lined one.
|
| NetworkManager, frankly, has no use on a typical server. Its dynamic
| manipulations of network configuration are unpredictable, unintuitive,
| and far more suited to a laptop or traveling desktop in an environment
| where upstream DHCP is reliably configured. It is a complex and
| powerful tool that *STILL* has no way to configure pair-bonding,
| 'bridged' connections for KVM supporting hosts, or DHCP client
| configuration with client identifiers except to use a text editor and
| turn off NetworkManager by one means or another. It's one of the
| upstream vendors least useful development efforts.
|
| Unfortunately, we're now pretty much stuck with it, due to all the
| recent system dependencies on it. Ripping it out by the roots became
| infeasible with Scientific :Linux 6. Fortunately, pre-configuring
| 'NM_CONTROLLED=no' is a new capability, and doing so early in the
| kickstart '%post' scripts seems to be very helpful in preventing such
| issues. In syntax:
|
|       grep -q ^NM_CONTROLLED= [filename] || \
|            echo 'NM_CONTROLLED=no' >> [filename]
|       sed -i 's/NM_CONTROLLED=.*/NM_CONTROLLED=no/g' [filename]
|
| Deducing the files to do this to is a bit more awkward, since you
| don't want to touch '.bak' files or '~' files, but there are functions
| to do that already available in the /etc/sysconfig/network-scripts/
| utiliti4es. Do you need help with that?

- --
Robert E. Blair, Room C221, Building 360
Argonne National Laboratory (High Energy Physics Division)
9700 South Cass Avenue, Argonne, IL 60439, USA
Phone: (630)-252-7545  FAX: (630)-252-5782
GnuPG Public Key: http://www.hep.anl.gov/reb/key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD4DBQFNn1IAOMIGC6x7/XQRArHQAKC3ou2RC19qeg401vU4Lz6ocwJ8ngCXaeqz
z1yTtl8N+iMCiieNaNT1pw==
=cauz
-----END PGP SIGNATURE-----


ATOM RSS1 RSS2