FS#31470 - [avahi] Missing symlink to avahi-daemon.service
Attached to Project:
Arch Linux
Opened by Gerardo Exequiel Pozzi (djgera) - Saturday, 08 September 2012, 16:34 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 10 October 2012, 02:13 GMT
Opened by Gerardo Exequiel Pozzi (djgera) - Saturday, 08 September 2012, 16:34 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 10 October 2012, 02:13 GMT
|
Details
I guess, "dbus-org.freedesktop.Avahi.service" should be a
symlink to "avahi-daemon.service" (in
/usr/lib/systemd/system), otherwise if some service like
cups request it via dbus activation and avahi-daemon is not
"enabled" will fail:
-- Sep 08 13:17:05 gerardo dbus[336]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' Sep 08 13:17:05 gerardo dbus-daemon[336]: dbus[336]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details. Sep 08 13:17:05 gerardo dbus[336]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details. -- creating a symlink (in /usr/lib/systemd/system) activation via dbus works without needed to enabling such service: -- Sep 08 13:18:04 gerardo dbus-daemon[336]: dbus[336]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' Sep 08 13:18:04 gerardo dbus[336]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' -- |
This task depends upon
Closed by Gaetan Bisson (vesath)
Wednesday, 10 October 2012, 02:13 GMT
Reason for closing: No response
Additional comments about closing: not sure what to do, upstream says nothing ==> do nothing
Wednesday, 10 October 2012, 02:13 GMT
Reason for closing: No response
Additional comments about closing: not sure what to do, upstream says nothing ==> do nothing
1) Suspose that there are no other services that needs avahi-daemon so you start avahi-daemon.service manually
2) Try to systemctl stop avahi-daemon.service, and avahi-daemon.service is reloaded again.
--
Warning: Stopping avahi-daemon.service, but it can still be activated by:
avahi-daemon.socket
Job canceled.
--
3) but if symlink does not exist, avahi-daemon is not reloaded when trying to stop (because of not such file or directory) BUG? so job is not canceled:
--
Warning: Stopping avahi-daemon.service, but it can still be activated by:
avahi-daemon.socket
--
or I am missing some concept?
On the other hand, manually starting it will start avahi-daemon.socket because of the Requires= (this part seems a bit odd to me). Does avahi have some sort of timeout mechanism where it will shutdown if inactive for a while?
I've never been too sure on how all the interactions between DBus and systemd happens, nor have I been a proper "desktop" user for this stuff to be relevant to my needs.
I guess no, does not have stop-on-inactive.
$ cat /usr/share/dbus-1/system-services/org.freedesktop.Avahi.service | grep Systemd
SystemdService=dbus-org.freedesktop.Avahi.service
$ cat /usr/share/dbus-1/system-services/org.freedesktop.colord-sane.service | grep Systemd
SystemdService=colord-sane.service
maybe such thing is intentional? who knows, the same thing happens with bluez, where SystemdService=dbus-org.bluez.service but such file does not exists, instead is an alias then when enabled is a symlink.
@Gaetan: so if you want to close this task, do it ;)
Anyhow, thanks for your time on this!