SCIENTIFIC-LINUX-USERS Archives

July 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
Mailling list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Tue, 5 Jul 2011 12:50:40 -0500
Reply-To:
Ken Teh <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=ISO-8859-1; format=flowed
Subject:
Re: NM_CONTROLLED?
From:
Ken Teh <[log in to unmask]>
MIME-Version:
1.0
In-Reply-To:
<[log in to unmask]>
Organization:
Argonne National Laboratory
Comments:
To: Tom H <[log in to unmask]> cc: [log in to unmask]
Parts/Attachments:
text/plain (20 lines) 
I suggest turning off the NetworkManager service if it is appropriate.  I set this parameter to "no"  thinking it would be sufficient but then I started getting all sorts of weird behaviors like the network interface would stop working.  To be honest, I did not investigate but then I was setting the machine up as a server and wanted the network interface on and to stay on after the machine boots.



On 07/05/2011 12:43 PM, Tom H wrote:
> On Tue, Jul 5, 2011 at 1:19 PM, Todd And Margo Chester
> <[log in to unmask]>  wrote:
>>
>> In SL 6.0, 64 bit, I have the following parameter in
>> my ifcfg-ethxxx called:
>>
>> NM_CONTROLLED=yes
>>
>> What is this?
>
> NM_CONTROLLED == controlled by Network Manager
>
> It's only effective if set to "no" in order not to have the NIC under
> NM's control.

ATOM RSS1 RSS2