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.
You can also specify a special button which activates or deactivates the mouse
display this message
don't fork to background
generate Linux input events
If you provide the --nodaemon option lircmd won't fork to background.
On Linux systems the --uinput option will enable automatic generation
of Linux input events. lircmd will open /dev/input/uinput and inject
the simulated mouse events into the Linux kernel rather than creating
the /dev/lircm device.
lircmd will use syslogd to output error messages. It depends on your
system configuration where they will show up.
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.
The documentation for
is maintained as html pages. They are located under html/ in the