Section: System Manager Manual (8)
Updated: Last change: Aug 2015
Return to Main Contents
lircrcd - Synchronize lircrc state among client applications.
lircrcd [options] config-file
reads the given .lircrc config file and synchronises the mode
that the LIRC clients such as irxevent(1),
etc., are in. Using
has to be explicitly
enabled in the lircrc config file by adding the following line at the
beginning of the file:
This must be done at the top-level file, not an included one. The lircrc_class
string (here "default") could actually be anything; clients using the same
string in their lircrc will be synchronized.
Display help message.
The --permission option gives the file permission of the Unix domain
socket lircrcd creates on startup in octal representation. Read the
documentation for chmod for further details. If no --permission option
is given when the socket is created the default is to give only the
user owning the file read and write permissions (0600 in octal
With the --output option you can select the Unix domain socket, which
lircrcd will create. The default is to create a socket in VARRUNDIR
(usually /var/run/lirc), see FILES.
lircrcd syntactically uses the same protocol as lircd described in the
lircd(8) manpage. It supports the following commands:
Each program connecting to lircrcd identifies itself using this program.
ident is the string that is used in the Prog = token inside
the .lircrc file.
When the client receives the code string from lircd it will send it to
lircrcd and will receive back the applicable config string from the
returned back which means that nothing (more) should happen in response
to code. This command is used each time the lirc_code2char()
function is called by a client.
lircrcd will return the current mode string.
lircrcd will set the actual mode, reflecting a mode in the .lircrc
lircrcd creates its socket(s) in the VARRUNDIR directory, usually
/var/run/lirc. The socket basename includes the user UID and the
string from the lircrc_class option.
The documentation for
is maintained as html pages. They are located under html/ in the
This document was created by
using the manual pages.
Time: 10:37:09 GMT, September 03, 2015