logkeys
logkeys copied to clipboard
kernc
Log input from multiple keyboards
Instead of using the first kbd entry found in /proc/bus/input/devices, you
could spawn threads to handle input from all kbd devices found.
The log files would just have to be named accordingly, to indicate which device
produced the keystroke data.
Also, you could have a thread that monitors the system to detect when new USB
or Bluetooth keyboards are attached to the system, then automatically spawn a
thread to log their input.
This ability would make logkeys quite a bit more powerful and flexible.
Regards,
Markus.
Original issue reported on code.google.com by [email protected] on 2 Aug 2010 at 3:46
I agree, and I'm putting it on the TODO list, low-prio, though.
Do you have an idea how to monitor the system to detect newly attached USB or
BT keyboards?
Original comment by [email protected] on 2 Aug 2010 at 4:10
- Changed state: Accepted
- Added labels: Priority-Low, Type-Enhancement
- Removed labels: Priority-Medium, Type-Defect
At the moment I do not know how to detect newly attached USB or BT keyboards. I
intend to research this over the next few days. It would be a handy feature for
some other stuff I am working on.
One way might be to have a thread that polls the /proc/bus/input/devices file,
to detect changes due to keyboards connected or disconnected. But this seems a
bit inelegant to me, there must be some way to directly receive OS
notifications of new devices.
Original comment by [email protected] on 2 Aug 2010 at 4:18
It looks like you can use some udev rules to run external programs when devices
are connected.
http://www.reactivated.net/writing_udev_rules.html#external-run
I'll have to sit down and read this in some detail :-)
Original comment by [email protected] on 2 Aug 2010 at 4:40
Issue 59 has been merged into this issue.
Original comment by [email protected] on 25 May 2011 at 9:30
Thanks, for your attention. Do you still develop this program?
Original comment by [email protected] on 27 May 2011 at 6:27
Time permitting, I am.
Not very actively, I have to admit, but once a year I manage an iteration, I
guess. :-)
Original comment by [email protected] on 27 May 2011 at 2:54
Issue 65 has been merged into this issue.
Original comment by [email protected] on 1 Aug 2011 at 11:07
workaround:
sudo logkeys -s -m mylang.map -d /dev/input/event1 -o log.1.txt
sudo rm /var/run/logkeys.pid
sudo logkeys -s -m mylang.map -d /dev/input/event2 -o log.2.txt
Original comment by [email protected] on 15 May 2015 at 5:53