New: avahi-autoipd not starting when using systemd-tempfiles

https://bugs.busybox.net/show_bug.cgi?id=10641

Bug ID: 10641
Summary: avahi-autoipd not starting when using
systemd-tempfiles
Product: buildroot
Version: 2017.08
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: posted at heine.so
CC: buildroot at uclibc.org
Target Milestone: ---

Hi,

I have a systemd based system. When I want to start avahi-autoipd it quits with the following message:

"stat(): No such file or directory"

I debugged a bit and found a typo in package/avahi/avahi_tmpfiles.conf

It should be "/tmp/avahi-autoipd" instead of "/tmp/avahi-autopid". (twisted ip/pi)

When I change this in my builded system in /usr/lib/tmpfiles.d/avahi.conf it seems to work fine after reboot.

So I guess nobody used the combination of avahi-autoipd and systemd since the commit in 2014. Or did I misunderstood something?

Regards,
Michael

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10641

Michael Heinemann <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

            Summary|avahi-autoipd not starting  |avahi-autoipd not starting
                   |when using                  |when using systemd-tmpfiles
                   |systemd-tempfiles           |

You are receiving this mail because:
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=10641

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #1 from Thomas Petazzoni <[email protected]> --- Thanks a lot for the bug report. Fixed in commit
https://git.buildroot.org/buildroot/commit/?id=c427ce4d9f54d9b6433969ecb0fc8a4a5a9ba9b5.

You are receiving this mail because:
You are on the CC list for the bug.