48
48
<A NAME="lbAD"> </A>
49
49
<H2>DESCRIPTION</H2>
51
The main task of lircd is to decode the infrared signals and provide an
52
uniform interface for client applications. Clients can connect to lircd
53
through a Unix domain socket which is located in /dev/lircd. Using this
54
socket they will get the infrared codes received by lircd and they can
55
send commands to lircd.
51
The main task of lircd is to decode the infrared signals and provide
52
an uniform interface for client applications. Clients can connect to
53
lircd through a Unix domain socket which is located in
54
/var/run/lirc/lircd. Using this ocket they will get the infrared
55
codes received by lircd and they can send commands to lircd.
57
57
<DT><B>-h</B> <B>--help</B><DD>
58
58
display this message
61
61
<DT><B>-n</B> <B>--nodaemon</B><DD>
62
62
don't fork to background
63
63
<DT><B>-p</B> <B>--permission</B>=<I>mode</I><DD>
64
file permissions for /dev/lircd
64
file permissions for /var/run/lirc/lircd
65
65
<DT><B>-H</B> <B>--driver</B>=<I>driver</I><DD>
67
67
<DT><B>-d</B> <B>--device</B>=<I>device</I><DD>
82
82
accept SIMULATE command
83
83
<DT><B>-u</B> <B>--uinput</B><DD>
84
84
generate Linux input events
85
<DT><B>-R</B> <B>--repeat-max</B>=<I>limit</I><DD>
86
allow at most this many repeats
86
88
<A NAME="lbAE"> </A>
89
The --permission option gives the file permission of /dev/lircd if it
90
has to be created in octal representation. Read the documentation for
91
chmod for further details. If no --permission option is given when the
92
socket is initially created the default is to give all users read and
93
write permissions (0666 in octal representation). If /dev/lircd already
94
exists this option has no effect.
91
The --permission option gives the file permission of
92
/var/run/lirc/lircd if it has to be created in octal
93
representation. Read the documentation for chmod for further
94
details. If no --permission option is given when the socket is
95
initially created the default is to give all users read and write
96
permissions (0666 in octal representation). If /var/run/lirc/lircd
97
already exists this option has no effect.
96
With the --device option you can select the character device which lircd
97
should read from. The default currently is /dev/lirc but it probably
98
will change in future.
99
With the --device option you can select the character device which
100
lircd should read from. The default currently is /dev/lirc but it
101
probably will change in future.
100
103
If you're using the dev/input driver, you can use <I>name=STRING</I> or
101
104
<I>phys=STRING</I> to select the device; lircd will look in /dev/input
116
119
The connecting lircd instance will receive IR events from the lircd
117
120
instance it connects to.
119
With the --output option you can select Unix domain socket, which lircd
120
will write remote key codes to. The default currently is /dev/lircd.
122
With the --output option you can select Unix domain socket, which
123
lircd will write remote key codes to. The default currently is
122
126
With the --pidfile option you can select the lircd daemon pid file.
123
The default currently is /var/run/lircd.pid.
127
The default currently is /var/run/lirc/lircd.pid.
125
129
With the --logfile option you can select the lircd daemon log file.
126
130
The default currently is /var/log/lircd. Note that this option will
145
149
was given a button in the lircd config file, e.g. if the button is
146
150
named KEY_1, the '1' key code will be generated. You will find a
147
151
complete list of possible button names in /usr/include/linux/input.h.
153
The --repeat-max option sets an upper limit to the number of repeats
154
when sending a signal. The current default is 600. A SEND_START
155
request will repeat the signal this many times. Also, if the number of
156
repeats in a SEND_ONCE request exceeds this number, it will be
157
replaced by this number.
148
158
<A NAME="lbAF"> </A>
152
The config file for lircd is located in /etc/lircd.conf. lircd
162
The config file for lircd is located in /etc/lirc/lircd.conf. lircd
153
163
has its own log file in /var/log/lircd (beginning with LIRC version
154
164
0.6.1 you can configure lircd to use syslogd for log messages; then it
155
165
depends on your system configuration where log messages will show up).
176
186
<CENTER>[<A HREF="http://www.lirc.org/">LIRC homepage</A>]<BR>
177
<I>The LIRC Manual, last update: 12-Oct-2008</I></CENTER>
187
<I>The LIRC Manual, last update: 24-May-2009</I></CENTER>
180
190
<TD WIDTH="15%"> <BR></TD>