Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9836] New: triggerhappy: systemd unit broken
Date: Wed, 26 Apr 2017 09:01:34 +0000	[thread overview]
Message-ID: <bug-9836-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 9836
           Summary: triggerhappy: systemd unit broken
           Product: buildroot
           Version: 2017.02.1
          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: ---

I'm using triggerhappy in combination with systemd and a bash based system (no
busybox).


The systemd unit fails with this error message:

"Error opening '/dev/input/event*': No such file or directory"


The systemd unit has the start command defined as follows:

ExecStart=/usr/sbin/thd --triggers /etc/triggerhappy/triggers.d --socket
/var/run/thd.socket --user nobody /dev/input/event*


If you run the command directly from bash it is working, I guess because bash
is already expanding the wildcard.


thd started supporting Wildcards in Version 0.5.0. with the option
"--deviceglob" [1]

before it proposed a wrapper script for the systemd unit added in this commit:
[2]

I don't know if the unit currently supplied with buildroot ever worked, but not
with the thd version currently used.

Since 0.5.0 the systemd unit should be like this: [3]


So I could supply a patch but I'm not sure what is preferable. Fix the systemd
unit supplied with the current version included in buildroot 2017.02.1. Or bump
the version and provide the new style unit?

Regards,
Michael

[1]https://github.com/wertarbyte/triggerhappy/commit/c9b6556bd45529eebfabcad3b843beb185aca5fc
[2]https://github.com/wertarbyte/triggerhappy/commit/47a9e4e842676c48d056aefe623af1d29a9b0e5e
[3]https://github.com/wertarbyte/triggerhappy/commit/06720d2305bedc7fcef8b18919f5c73a73164f85

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

             reply	other threads:[~2017-04-26  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-26  9:01 bugzilla at busybox.net [this message]
2017-04-26  9:20 ` [Buildroot] [Bug 9836] triggerhappy: systemd unit broken bugzilla at busybox.net
2017-04-26 15:07 ` bugzilla at busybox.net
2017-05-07 14:06 ` bugzilla at busybox.net
2017-05-08 12:23 ` 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-9836-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox