1EVEMU-DESCRIBE(1) EVEMU-DESCRIBE(1)
2
3
4
6 evemu-describe, evemu-record - print information and events from an
7 input device
8
10 evemu-describe [/dev/input/eventX] [output file]
11
12 evemu-record [--autorestart=s] [/dev/input/eventX] [output file]
13
15 evemu-describe gathers information about the input device and prints it
16 to stdout. This information can be parsed by evemu-device(1) to create
17 a virtual input device with the same properties.
18
19 evemu-record captures events from the input device and prints them to
20 stdout. The events can be parsed by evemu-play(1) to let a virtual
21 input device created with evemu-device(1) emit the exact same event
22 sequence.
23
24 evemu-describe and evemu-record need to be able to read from the
25 device; in most cases this means they must be run as root.
26
27 If an event node is provided, evemu-describe and evemu-record use that
28 event node. Otherwise, the user must interactively choose from a list
29 of detected devices.
30
31 If no output file is given, stdout is used.
32
34 --autorestart=<s>
35 Terminate the current recording after <s> seconds of device
36 inactivity. This option requires an output, the file is suffixed
37 with the date and time of the recording's start.
38 The timeout must be greater than 0.
39
41 If evtest-record does not see any events even though the device is
42 being used, the device may be grabbed by a process (EVIOCGRAB). This is
43 usually the case when debugging a synaptics or wacom device from within
44 X. VT switching to a TTY or shutting down the X server terminates this
45 grab and the devices can be recorded. For most X drivers, disabling the
46 device also removes the grab.
47
48 The following command shows the processes with an open file descriptor
49 on the device.
50
51 fuser -v /dev/input/eventX
52
54 evemu-device(1) evemu-play(1)
55
57 evemu was written by Henrik Rydberg <rydberg@euromail.se[1]>
58
60 1. rydberg@euromail.se
61 mailto:rydberg@euromail.se
62
63
64
65 09/25/2017 EVEMU-DESCRIBE(1)