Summary: | Confusion on Debian where /etc/init.d/avahi-daemon Provides avahi | ||
---|---|---|---|
Product: | systemd | Reporter: | Joachim Breitner <mail> |
Component: | general | Assignee: | Lennart Poettering <lennart> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Joachim Breitner
2010-10-13 14:06:31 UTC
Since avahi-daemon in Debian ships a native systemd service file, I should probably just add a Alias=avahi.service to [Install] so those LSB/SysV services which have a Should-Start: avahi have proper ordering. That said, avahi uses socket activation, so this explicit ordering isn't actually needed anymore and it is merely a cosmetic issue. So I'm inclined to just close this upstream bug. If at all, this is something that should be dealt with in the Debian avahi package. This is a bug in your distribution 's packages, if still around after please fill a bug report in the debian BTS, thank you. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.