NetworkManager is started itself

English Network/Internet
1

In Yast -> Services Manager the services: NetworkManager, NetworkManager-dispatcher, NetworkManager-wait-online are setup to start “Manually”.
In Yast -> Network Settings: Global Options -> Network Setup Method is Wicked Service.
But last about 2 days after boot i see, that NM applet is active, NM service is run, and respectively settings from NM is applied. Also from boot logs i notice NetworkManager-wait-online to be started.

So, i manually stop NetworkManager service, also do


sudo systemctl restart network.service

and my network settings is ok.

How can i prevent to NM starting itself?

2

Post:

systemctl status NetworkManager.service
3 

systemctl status NetworkManager.service

● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
           └─NetworkManager-ovs.conf
   Active: inactive (dead) since Fri 2019-04-12 12:53:26 MSK; 6h ago
     Docs: man:NetworkManager(8)
 Main PID: 785 (code=exited, status=0/SUCCESS)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           └─1215 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth1.pid -lf /var/lib/NetworkManager/dhclient-8b47315f-31cb-3405-ad06-8d4a2c08595e-eth1.lease -cf /var/lib/NetworkManager/dhclient-eth1.conf eth1
4

To list other unit files that depend on NetworkManager.service, run

 systemctl list-dependencies NetworkManager --reverse

You can follow this chain to find further unit files that may have triggered those dependencies if necessary eg NetworkManager-wait-online…

systemctl list-dependencies NetworkManager-wait-online --reverse
5

Don’t configure those NM services to be “Manual,” configure them “Disabled”

TSU

6

List network.target:

erlangen:~ # systemctl list-dependencies network.target --reverse 
network.target
● ├─chronyd.service
● ├─ntpd.service
● └─systemd-networkd.service
erlangen:~ #

Make sure all of these are disabled:

erlangen:~ # systemctl list-unit-files 'NetworkManager*'
UNIT FILE                          STATE   
NetworkManager-dispatcher.service  disabled
NetworkManager-wait-online.service disabled
NetworkManager.service             disabled

3 unit files listed.
erlangen:~ #

Switched from wicked/NetworkManager to systemd-networkd weeks ago. Since then only networkd got invoked.

7 

systemctl list-dependencies NetworkManager-wait-online --reverse
NetworkManager-wait-online.service
● └─teamviewerd.service

Yes, several days ago i’ve installed teamviewer. Seems this is the reason.

8

Yast Services Manager offers only “On Boot” and “Manually”.

9

Yast2 lan > Global Options has NetworkManager, wicked and disabled.

10

I actually use Wicked service. I would not like to disable it.

I set start mode for teamviewerd.service to be manually. Now, NM is not started on boot itself. Consider the problem is solved. Thanks, everyone!

11

Glad to have been of help! :slight_smile: