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
|
.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.24.
.TH LIRCMD "1" "February 2005" "lircmd 0.7.1pre2" FSF
.SH NAME
LIRC mouse daemon - translates infrared signals into mouse events
.SH SYNOPSIS
.B lircmd
\fI0.7.1pre2 \fR[\fIoptions\fR] [\fIconfig-file\fR]
.SH DESCRIPTION
This daemon can simulate a MouseSystems, IntelliMouse or IMPS/2 type mouse. It
gets the received buttons from lircd and converts them to mouse events. To
make this possible, lircmd needs a config file located
in /etc/lircmd.conf. In this file you have to determine which
button from which remote causes a mouse move or a mouse button click.
.TP
\fB\-h\fR \fB\-\-help\fR
display this message
.TP
\fB\-v\fR \fB\-\-version\fR
display version
.TP
\fB\-n\fR \fB\-\-nodaemon\fR
don't fork to background
.SH OPTIONS
If you provide the --nodaemon option lircmd won't fork to background.
.SH FILES
lircmd will use syslogd to output error messages. It depends on your
system configuration where they will show up.
.SH DAEMONS
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.
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.
.SH "SEE ALSO"
The documentation for
.B lirc
is maintained as html pages. They are located under html/ in the
documentation directory.
|
