inputlircd(8) [debian man page]
INPUTLIRCD(8) BSD System Manager's Manual INPUTLIRCD(8) NAME
inputlircd -- zeroconf LIRC daemon using input event devices SYNOPSIS
inputlircd [-d socket] [-f] [-c] [-r repeat-rate] [-m keycode] [-n device name] [-u username] device [device ...] DESCRIPTION
inputlircd is a small LIRC daemon that reads from /dev/input/eventX devices and sends the received keycodes to connecting LIRC clients. inputlircd needs no configuration, it uses the standardised names for the keycodes as used by the kernel. Many USB remote controls that present HID devices, as well as multimedia keyboards should work out of the box. inputlircd expects a list of input event devices as commandline parameters. It will only read events from those devices. OPTIONS
-d socket Location of the UNIX socket to which LIRC clients can connect. The default is /var/run/lirc/lircd. -f Run in the foreground. -c Capture modifier keys. This causes the CTRL, SHIFT, ALT and META keys to be treated as modifer keys that, when used in combination with another keys, change the LIRC event from that key rather than being sent as their own LIRC events. -r repeat-rate Set the repeat rate (in milliseconds) of the remote control. The default is 0. Repeated keys that arrive less than repeat-rate mil- liseconds apart will be flagged as as repeat LIRC events. -g Grab the input device(s). This gives inputlircd exclusive access to the input devices and stops events from propagating any further. -m keycode Minimum keycode to send to LIRC clients. Keycodes lower than this number are filtered out. The default is 88, this filters out the alphanumeric section and the keypad section of normal keyboards, but allows all extended keys. The rationale is that clients should not be able to grab normal keypresses, this could be a security risk. -n device name Name of an input device to read events from. This scans all available input event devices, and if the symbolic name of an event device matches device name, adds it to the list of devices to read from. The device name can contain wildcard patterns, see glob(7). To get a list of available devices and their names, cat /proc/bus/input/devices or use lsinput(8). -u username Set user and group id to that of username after opening the devices and UNIX socket as root. The default is nobody. -t path Provides the path to a file containing a mapping between input event key names and the commands which should be reported via lirc. The files should contain lines of the form KEY_FOO = bar. This is useful for backward compatibility. The default is not to use a transla- tion table. device One or more input event devices. If you want to use inputlircd to process multimedia keys on the keyboard, then /dev/input/event0 is the most likely choice. If you have other input devices, such as USB remote controllers that act like a HID device, then you probably need one of the other event devices present. See /proc/bus/input/devices for a list of available input devices. If unsure, you can add all available input event devices. FILES
/var/run/lirc/lircd Default location of the UNIX socket to which LIRC clients can connect. /dev/input/eventX The kernel input layer's event device files. /proc/bus/input/devices List of all input devices. SEE ALSO
irw(1), input-events(8), setkeycodes(8), /usr/include/linux/input.h. June 1, 2019
Check Out this Related Man Page
LIRCD(8) FSF LIRCD(8) NAME
lircd - LIRC daemon decodes infrared signals and provides them on a Unix domain socket. SYNOPSIS
lircd [options] [config-file] DESCRIPTION
The main task of lircd is to decode the infrared signals and provide an uniform interface for client applications. Clients can connect to lircd through a Unix domain socket which is located in var/run/lirc/lircd. Using this ocket they will get the infrared codes received by lircd and they can send commands to lircd. -h --help display this message -v --version display version -n --nodaemon don't fork to background -p --permission=mode file permissions for /var/run/lirc/lircd -H --driver=driver use given driver -d --device=device read from given device -l --listen[=[address:]port] listen for network connections -c --connect=host[:port] connect to remote lircd server -o --output=socket output socket filename -P --pidfile=file daemon pid file -L --logfile=file daemon log file -r --release[=suffix] auto-generate release events -a --allow-simulate accept SIMULATE command -u --uinput generate Linux input events -R --repeat-max=limit allow at most this many repeats OPTIONS
The --permission option gives the file permission of var/run/lirc/lircd if it has to be created in octal representation. Read the documen- tation for chmod for further details. If no --permission option is given when the socket is initially created the default is to give all users read and write permissions (0666 in octal representation). If /var/run/lirc/lircd already exists this option has no effect. With the --device option you can select the character device which lircd should read from. The default currently is /dev/lirc but it proba- bly will change in future. If you're using the dev/input driver, you can use name=STRING or phys=STRING to select the device; lircd will look in /dev/input to find a device with a matching description. This is useful in case the device name isn't fixed. STRING may contain the '*' and '?' wildcards and '' to mark them as literal. With the --listen option you can let lircd listen for network connections on the given address/port. The default address is 0.0.0.0, which means that connections on all network interfaces will be accepted. The default port is 8765. No security checks are currently implemented. The listening lircd instance will send all IR events to the connecting lircd instances. The --connect option allows you to connect to other lircd servers that provide a network socket at the given host and port number. The num- ber of such connections is currently limited to 100. The connecting lircd instance will receive IR events from the lircd instance it con- nects to. With the --output option you can select Unix domain socket, which lircd will write remote key codes to. The default currently is var/run/lirc/lircd. With the --pidfile option you can select the lircd daemon pid file. The default currently is /var/run/lirc/lircd.pid. With the --logfile option you can select the lircd daemon log file. The default currently is /var/log/lircd. Note that this option will only be available if you compiled lircd without syslog support. The --release option enables automatic generation of release events for each button press. lircd will append the given suffix to the button name for each release event. If no suffix is given the default suffix is '_UP'. The --allow-simulate option will enable the SIMULATE command which can be issued using irsend(1). This will allow simulating arbitrary IR events from the command line. Use this option with caution because it will give all users with access to the lircd socket wide control over you system. E.g. if you have configured your system to shut down by a button press on your remote control, everybody will be able to shut down your system from the command line. On Linux systems the --uinput option will enable automatic generation of Linux input events. lircd will open /dev/input/uinput and inject key events to the Linux kernel. The key code depends on the name that was given a button in the lircd config file, e.g. if the button is named KEY_1, the '1' key code will be generated. You will find a complete list of possible button names in /usr/include/linux/input.h. The --repeat-max option sets an upper limit to the number of repeats when sending a signal. The current default is 600. A SEND_START request will repeat the signal this many times. Also, if the number of repeats in a SEND_ONCE request exceeds this number, it will be replaced by this number. FILES
The config file for lircd is located in /etc/lirc/lircd.conf. lircd has its own log file in /var/log/lircd (beginning with LIRC version 0.6.1 you can configure lircd to use syslogd for log messages; then it depends on your system configuration where log messages will show up). You can make lircd reread its config file and reopen its log file by sending the HUP signal to the program. That way you can rotate old log files. DAEMONS
lircd and lircmd are daemons. You should start them in some init script depending on your system. There are some example scripts for dif- ferent distributions in the contrib directory. lircmd has to be started after lircd as it connects to the socket lircd provides. If you start lircd or lircmd from your shell prompt you will usually get back immediately to the prompt. Often people think that the pro- gram has died. But this is not an error. lircd and lircmd are daemons. Daemons always run in background. SEE ALSO
The documentation for lirc is maintained as html pages. They are located under html/ in the documentation directory. lircd 0.8.7pre1 May 2010 LIRCD(8)