Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36975 - NetworkManager creating service symlink in /etc/systemd/system

Attached to Project: Arch Linux
Opened by Robert Orzanna (orschiro) - Wednesday, 18 September 2013, 13:04 GMT
Last edited by Dave Reisner (falconindy) - Wednesday, 18 September 2013, 13:32 GMT
Task Type General Gripe
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I wonder why NetworkManager creates a service symlink directly inside of /etc/systemd/system. See the following output:

[orschiro@thinkpad ~]$ sudo systemctl enable NetworkManager-dispatcher
[sudo] password for orschiro:
ln -s '/usr/lib/systemd/system/NetworkManager-dispatcher.service' '/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service'
ln -s '/usr/lib/systemd/system/NetworkManager-dispatcher.service' '/etc/systemd/system/multi-user.target.wants/NetworkManager-dispatcher.service'

I thought that all service symlinks should be placed inside of the *.target.wants directories but not directly in /system/.

Can anyone explain me why this symlink `dbus-org.freedesktop.nm-dispatcher.service` is created?

Additional info:
* package version(s)
* config and/or log files etc.

systemd 204-3
networkmanager 0.9.8.2-1
This task depends upon

Closed by  Dave Reisner (falconindy)
Wednesday, 18 September 2013, 13:32 GMT
Reason for closing:  None
Comment by Dave Reisner (falconindy) - Wednesday, 18 September 2013, 13:32 GMT
Because it's a dbus busname alias. Units don't need to be in a .wants or .requires directory in order to be activated.

Loading...