All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10641] New: avahi-autoipd not starting when using systemd-tempfiles
Date: Wed, 10 Jan 2018 16:45:33 +0000	[thread overview]
Message-ID: <bug-10641-163@https.bugs.busybox.net/> (raw)

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.

             reply	other threads:[~2018-01-10 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 16:45 bugzilla at busybox.net [this message]
2018-01-10 16:45 ` [Buildroot] [Bug 10641] avahi-autoipd not starting when using systemd-tmpfiles bugzilla at busybox.net
2018-01-10 19:55 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-10641-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.