Public bug reported:
Version: 1.10.6-2ubuntu1
Ubuntu release: 18.04
I've just had a fun few minutes wondering why I couldn't disable NM
using "systemctl disable network-manager.service". Looks like the real
unit file is NetworkManager.service, and the former is a symlink.
Per systemd.unit(5), "unit files may specify aliases through the Alias=
directive in the [Install] section" which allows the aliases to be used
in systemctl disable etc. - so this might be a cleaner approach and
would presumably solve the problem of lusers like me guessing unit names
..
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1782033
Title:
"Alias=" missing from NetworkManager.service
Status in network-manager package in Ubuntu:
New
Bug description:
Version: 1.10.6-2ubuntu1
Ubuntu release: 18.04
I've just had a fun few minutes wondering why I couldn't disable NM
using "systemctl disable network-manager.service". Looks like the real
unit file is NetworkManager.service, and the former is a symlink.
Per systemd.unit(5), "unit files may specify aliases through the
Alias= directive in the [Install] section" which allows the aliases to
be used in systemctl disable etc. - so this might be a cleaner
approach and would presumably solve the problem of lusers like me
guessing unit names ..
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1782033/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
