Two pits-linux under Network-manager wired unmanaged-dns resolv.conf file is emptied

Linux has two sets of programs to manage network connectivity:

1,/etc/network/interfaces (/etc/init.d/networking) 2, Network-manager

Two sets of schemes are conflicting and cannot coexist at the same time.

The first scenario is for environments that do not have x, such as servers, or where there is no need to change connections at All. The second set of programs used in the desktop environment, especially notebooks, moved to move around, the network connection situation will change at any Time.

Both of them to avoid conflicts and to share the configuration, there is the following solution:

1. When Network-manager discovers That/etc/network/interfaces was altered, it closes itself (shown as Unmanaged) unless the managed is set to True.

2, when the managed is set to true,/etc/network/interfaces, it does not take effect. ############## sudo vi/etc/networkmanager/networkmanager.conf change the managed=false to true, restart it. ##############

Two pits

1. Wired Unmanaged

If you have already configured eth0 in/etc/network/interfaces, you need to remove the eth0 configuration and modify/etc/networkmanager/networkmanager.conf managed=true

Reboot

Cause: interfaces configured the eth0 so that the Network-manager thought interfaces took over the network control, so in order to avoid the conflict, no longer take over eth0, so the display device is not hosted.

2,/etc/resolv.conf Boot is emptied

The reason is Ditto.

Two pits-linux under Network-manager wired unmanaged-dns resolv.conf file is emptied