There is no difference.
The unit file for network-manager.service is a symlink to NetworkManager.service.
$ file $(locate network-manager.service)
/lib/systemd/system/network-manager.service: symbolic link to NetworkManager.service
The "two" services are the same process:
$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2017-05-28 06:51:58 BST; 25min ago
Docs: man:NetworkManager(8)
Main PID: 667 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─ 667 /usr/sbin/NetworkManager --no-daemon
└─1277 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient
$ systemctl status network-manager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2017-05-28 06:51:58 BST; 25min ago
Docs: man:NetworkManager(8)
Main PID: 667 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─ 667 /usr/sbin/NetworkManager --no-daemon
└─1277 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient
The name network-manager remains simply for compatibility, so people can use old style commands like sudo service network-manager restart (sympathy for our muscle memory).
sudo systemctl status network-manager.servicereturnsactivewhilesudo systemctl status NetworkManager.servicereturnsinactive(dead)– Rtsne42 May 28 '17 at 06:38inactive(dead)Screenshot . – Rtsne42 May 28 '17 at 06:46$ sudo service network-manager restart
Failed to restart network-manager.service: Unit network-manager.service not found.
– Good Pen May 19 '23 at 09:37