SCIENTIFIC-LINUX-USERS Archives

August 2012

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:
Nico Kadel-Garcia <[log in to unmask]>
Reply To:
Nico Kadel-Garcia <[log in to unmask]>
Date:
Fri, 3 Aug 2012 16:15:24 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
On Fri, Aug 3, 2012 at 2:15 PM, Konstantin Olchanski <[log in to unmask]> wrote:
> On Thu, Aug 02, 2012 at 06:51:11PM +0000, Adam Bishop wrote:
>> Yesterday afternoon the core router on our network decided to have a short nap and stopped routing packets for an hour or so. Layer 2 connectivity was not affected.
>>
>> As the DHCP server is on a different VLAN to most of my SL servers, a few of them were unable to renew their DHCP leases.
>
>
> If you are using SL6 and the NetworkManager: https://bugzilla.redhat.com/show_bug.cgi?id=829499

If you're using NetworkManager for *anything* on a server, don't. It's
fragile and destabilizing. Its main use is in highly dynamic
environments, such as laptops hopping from access point to network to
VPN to local wire connection to modem to who knows what.

I find it safest to simply delete it, but if you've software that
demands NetworkManager, use "/sbin/chkconfig off NetworkManager" to
disable it and put 'NM_CONTROLLED=no' in your /etc/sysconfig/ifcfg-*
files to block it, even if it's accidentally run.

ATOM RSS1 RSS2