1LIRCD(1)                              FSF                             LIRCD(1)
2
3
4

NAME

6       LIRC  daemon  -  decodes  infrared  signals and provides them on a Unix
7       domain socket.
8

SYNOPSIS

10       lircd [options] [config-file]
11

DESCRIPTION

13       The main task of lircd is to decode the infrared signals and provide an
14       uniform interface for client applications. Clients can connect to lircd
15       through a Unix domain socket which is located in /dev/lircd. Using this
16       socket  they will get the infrared codes received by lircd and they can
17       send commands to lircd.
18
19       -h --help
20              display this message
21
22       -v --version
23              display version
24
25       -n --nodaemon
26              don't fork to background
27
28       -p --permission=mode
29              file permissions for /dev/lircd
30
31       -H --driver=driver
32              use given driver
33
34       -d --device=device
35              read from given device
36
37       -l --listen[=port]
38              listen for network connections on port
39
40       -c --connect=host[:port]
41              connect to remote lircd server
42
43       -o --output=socket
44              output socket filename
45
46       -P --pidfile=file
47              daemon pid file
48
49       -L --logfile=file
50              daemon log file
51
52       -r --release[=suffix]
53              auto-generate release events
54

OPTIONS

56       The --permission option gives the file permission of /dev/lircd  if  it
57       has  to  be created in octal representation. Read the documentation for
58       chmod for further details. If no --permission option is given when  the
59       socket  is  initially created the default is to give all users read and
60       write permissions (0666 in octal representation). If /dev/lircd already
61       exists this option has no effect.
62
63       With  the  --device  option  you  can select the character device which
64       lircd should read from. The default currently is /dev/lirc but it prob‐
65       ably will change in future.
66
67       If  you're  using  the  dev/input  driver,  you  can use name=STRING or
68       phys=STRING to select the device; lircd will look in /dev/input to find
69       a device with a matching description. This is useful in case the device
70       name isn't fixed. STRING may contain the '*' and '?'  wildcards and '\'
71       to mark them as literal.
72
73       With  the  --listen option you can let lircd listen for network connec‐
74       tions on the given port. The default port is 8765. No  security  checks
75       are currently implemented.
76
77       The  --connect option allows you to connect to other lircd servers that
78       provide a network socket at the given host and port number. The  number
79       of such connections is currently limited to 100.
80
81       With the --output option you can select Unix domain socket, which lircd
82       will write remote key codes to. The default currently is /dev/lircd.
83
84       With the --pidfile option you can select the  lircd  daemon  pid  file.
85       The default currently is /var/run/lircd.pid.
86
87       With  the  --logfile  option  you can select the lircd daemon log file.
88       The default currently is /var/log/lircd. Note  that  this  option  will
89       only be available if you compiled lircd without syslog support.
90
91       The --release option enables automatic generation of release events for
92       each button press. lircd will append the given  suffix  to  the  button
93       name  for  each release event. If no suffix is given the default suffix
94       is '_UP'.
95

FILES

97       The config file for lircd is located in /etc/lircd.conf. lircd has  its
98       own  log  file in /var/log/lircd (beginning with LIRC version 0.6.1 you
99       can configure lircd to use syslogd for log messages; then it depends on
100       your  system  configuration  where log messages will show up).  You can
101       make lircd reread its config file and reopen its log  file  by  sending
102       the HUP signal to the program. That way you can rotate old log files.
103

DAEMONS

105       lircd and lircmd are daemons. You should start them in some init script
106       depending on your system. There are some example scripts for  different
107       distributions  in the contrib directory. lircmd has to be started after
108       lircd as it connects to the socket lircd provides.
109
110       If you start lircd or lircmd from your shell prompt  you  will  usually
111       get back immediately to the prompt. Often people think that the program
112       has died. But this is not an error. lircd and lircmd are daemons.  Dae‐
113       mons always run in background.
114

SEE ALSO

116       The  documentation  for  lirc  is  maintained  as  html pages. They are
117       located under html/ in the documentation directory.
118
119
120
121lircd 0.8.2                        June 2007                          LIRCD(1)
Impressum