Bugzilla – Bug 801994
NetworkManager disabled in config but still trying to start
Last modified: 2013-02-18 13:50:35 UTC
looks like the NETWORKMANAGER variable is gone from /etc/sysconfig/network/config is there any other way to disable NM other than installing the whole tree of packages starting at NetworkManager (I assume getting NM to setup a trunk of vlans plus the bridges and interfaces on top is out of the question)
just found in 12.3-RC1 as well, that in spite of switching to ifup mode in yast systemctl status NetworkManager.service still shows it as enabled (so starting on boot) systemctl disable NetworkManager.service might be a workaround
sysconfig and most other packages has been changed to not use NETWORKMANAGER variable any more, but a network.service alias link. See also release notes bug #800771 and - still unfixed - bug #798348, to adopt switching between NetworkManager and /etc/init.d/network in yast2. [/etc/init.d/network is currently active only while miminal installation, in all other cases NetworkManager because yast2 is unable to switch it as needed.] To enable NetworkManager, use: systemctl stop network.service systemctl --force enable NetworkManager.service systemctl start network.service to disable NetworkManager, use: systemctl stop network.service systemctl --force disable NetworkManager.service systemctl start network.service This command: systemctl --no-pager -p Id show network.service reports "Id=NetworkManager.service" when NetworkManager acts as the network service, "Id=network.service" means /etc/init.d/network. *** This bug has been marked as a duplicate of bug 798348 ***