Reproduced on NM_CONTROLLED and Network Manager
Redhat in RHEL 6 (Redhat Enterprise Linux), engage on a Network manger service (also affects CentOs corresponding version)
is said to facilitate the management of wireless Wifi, maybe it normal desktop users of some use,
but to rely heavily on the network, regular system administrators to remotely manage, this thing is a disaster.
. 1
when installing the operating system, the card automatically generated configuration file,
/ etc / sysconfig / Network-scripts / the ifcfg-eth0
which has the following parameters:
NM_CONTROLLED = Yes
DESCRIPTION Network manger default service is activated,
#chkconfig --list | grep NetworkManager
NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
#service NetworkManager status
NetworkManager (pid 1634) is running...
- 1
- 2
- 3
- 4
- 5
When the system administrator according to previous habits, on a remote terminal connection, modify ifcfg-eth0 file, the network may immediately interrupt, causing crashes remote connection, you can not do anything.
Administrators can only go to the engine room (if you're lucky, more recent words from the engine room), Terminal Server Console to make changes.
This is because NM_CONTROLLED parameter network manger, which is effective immediately, and no need to restart the network service (or card) modified,
if NM_CONTROLLED = yes, when you modify the content of ifcfg-ethx file, if the content is not entirely correct, there is a high probability lead to network outages.
2
for servers, workstations, clusters, virtual machines, the general should turn off the NetworkManager service:
#service NetworkManager status
NetworkManager (pid 1634) is running...
#service NetworkManager stop
Stopping NetworkManager daemon: [ OK ]
#chkconfig NetworkManager off
#chkconfig --list | grep NetworkManager
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
- 1
- 2
- 3
- 4
- 5
- 6
- 7
Meanwhile, modify / etc / sysconfig / network-scripts / ifcfg-eth0 other documents:
NM_CONTROLLED = NO