1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE>LIRC - Linux Infrared Remote Control</TITLE>
<LINK REL=stylesheet TYPE="text/css" HREF="../lirc.css">
<LINK REL="shortcut icon" HREF="../favicon.ico">
<META NAME="description" CONTENT="LIRC - Linux Infra-red Remote Control">
<META NAME="keywords" CONTENT="linux, kernel module, remote control, animax, multimedia">
</HEAD>
<BODY BACKGROUND="../images/marb18.jpg"
BGCOLOR="#FFFFFF" TEXT="#000000" ALINK="#8080FF">
<TABLE WIDTH="100%" BORDER="0" CELLSPACING="0" CELLPADDING="0">
<TR>
<TD CLASS="menu" WIDTH="100%" HEIGHT="150">
<IMG SRC="../images/diode.gif" ALT=""
WIDTH="300" HEIGHT="150" BORDER="0" HSPACE="20"
VSPACE="0" ALIGN="LEFT">
<IMG SRC="../images/lirc.gif" ALT=""
WIDTH="300" HEIGHT="150" BORDER="0" HSPACE="20"
VSPACE="0" ALIGN="RIGHT">
</TD>
</TR>
<TR>
<TD WIDTH="100%"> <BR>
<TABLE WIDTH="100%" BORDER="0" CELLSPACING="0" CELLPADDING="0">
<TR>
<TD WIDTH="15%"> <BR></TD>
<TD WIDTH="70%" ALIGN="LEFT" VALIGN="TOP"> <BR>
<!-- Text ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<H1>LIRCD</H1>
<HR>
<A NAME="lbAB"> </A>
<H2>NAME</H2>
LIRC daemon - decodes infrared signals and provides them on a Unix
domain socket.
<A NAME="lbAC"> </A>
<H2>SYNOPSIS</H2>
<B>lircd</B>
<I>0.7.1pre2 </I>[<I>options</I>] [<I>config-file</I>]
<A NAME="lbAD"> </A>
<H2>DESCRIPTION</H2>
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 /dev/lircd. Using this
socket they will get the infrared codes received by lircd and they can
send commands to lircd.
<DL COMPACT>
<DT><B>-h</B> <B>--help</B><DD>
display this message
<DT><B>-v</B> <B>--version</B><DD>
display version
<DT><B>-n</B> <B>--nodaemon</B><DD>
don't fork to background
<DT><B>-p</B> <B>--permission</B>=<I>mode</I><DD>
file permissions for /dev/lircd
<DT><B>-H</B> <B>--driver</B>=<I>driver</I><DD>
use given driver
<DT><B>-d</B> <B>--device</B>=<I>device</I><DD>
read from given device
<DT><B>-l</B> <B>--listen</B>[=<I>port</I>]<DD>
listen for network connections on port
<DT><B>-c</B> <B>--connect</B>=<I>host[</I>:port]<DD>
connect to remote lircd server
<DT><B>-o</B> <B>--output</B>=<I>socket</I><DD>
output socket filename
<DT><B>-P</B> <B>--pidfile</B>=<I>file</I><DD>
daemon pid file
<DT><B>-L</B> <B>--logfile</B>=<I>file</I><DD>
daemon log file
<DT>
<B>-D[debug_level]</B> <B>--debug</B>[=<I>debug_level</I>]
</DL>
<A NAME="lbAE"> </A>
<H2>OPTIONS</H2>
<DD>The --permission option gives the file permission of /dev/lircd if it
has to be created in octal representation. Read the documentation 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 /dev/lircd already
exists this option has no effect.
<P>
With the --device option you can select the character device which lircd
should read from. The default currently is /dev/lirc but it probably
will change in future.
<P>
With the --listen option you can let lircd listen for network
connections on the given port. The default port is 8765. No security
checks are currently implemented.
<P>
The --connect option allows you to connect to other lircd servers that
provide a network socket at the given host and port number. The number
of such connections is currently limited to 100.
<P>
With the --output option you can select Unix domain socket, which lircd
will write remote key codes to. The default currently is /dev/lircd.
<P>
With the --pidfile option you can select the lircd daemon pid file.
The default currently is /var/run/lircd.pid.
<P>
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.
<A NAME="lbAF"> </A>
<H2>FILES</H2>
<P>
The config file for lircd is located in /etc/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.
<A NAME="lbAG"> </A>
<H2>DAEMONS</H2>
lircd and lircmd are daemons. You should start them in some init script
depending on your system. There are some example scripts for different
distributions in the contrib directory. lircmd has to be started after
lircd as it connects to the socket lircd provides.
<P>
If you start lircd or lircmd from your shell prompt you will usually get
back immediately to the prompt. Often people think that the program has
died. But this is not an error. lircd and lircmd are daemons. Daemons
always run in background.
<A NAME="lbAH"> </A>
<!-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
<BR><BR>
<CENTER>[<A HREF="http://www.lirc.org/">LIRC homepage</A>]<BR>
<I>The LIRC Manual, last update: 12-Sep-2002</I></CENTER>
<BR><BR>
</TD>
<TD WIDTH="15%"> <BR></TD>
</TR>
</TABLE>
</TD>
</TR>
<TR>
<TD CLASS="menu" WIDTH="100%"> <BR>
</TD>
</TR>
</TABLE>
</BODY>
</HTML>
|
