[Bug 10131] New: acpid should monitor /sys/class/input for new devices
bugzilla at busybox.net
bugzilla at busybox.net
Wed Jul 26 02:05:27 UTC 2017
https://bugs.busybox.net/show_bug.cgi?id=10131
Bug ID: 10131
Summary: acpid should monitor /sys/class/input for new devices
Product: Busybox
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
Assignee: unassigned at busybox.net
Reporter: clayton at craftyguy.net
CC: busybox-cvs at busybox.net
Target Milestone: ---
Currently, acpid will read in /sys/class/input/eventX devices on startup and
will not detect any new ones. This is problematic for two reasons:
1) If a new input device is added and the user wants to manage events from it
with acpid, they would have to restart acpid (they may not always have the
privileges required for this)
2) I have a device which, for one reason or another, actually starts acpid
before the kernel has finished modprobing/enabling input devices, so quite a
few buttons/switches events are never handled by acpid unless acpid is
restarted.
On the busybox mailing list, it was suggested that using inotify might be one
option, since big acpid apparently uses it. I wrote a patch that basically
polls for new devices in the existing main loop in acpid, but I haven't been
able to test it for completely unrelated-to-busybox reasons.. so I'm refraining
from sharing it here unless there is interest.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the busybox-cvs
mailing list