Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Linux Magazine: The source for advanced Linux know-how

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
Copyright Info
Terms of Use
Privacy Info
Masthead / Impressum
Your Account

Private Messages

News Archive
Submit News
User Articles
Web Links


The Web

Who's Online
There are currently, 65 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here




       lircd 0.6.6 [options] [config-file]


       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.

       -h --help
              display this message

       -v --version
              display version

       -n --nodaemon
              don't fork to background

       -p --permission=mode
              file permissions for /dev/lircd

       -H --driver=driver
              use given driver

       -d --device=device
              read from given device

       -l --listen[=port]
              listen for network connections on port

       -c --connect=host[:port]
              connect to remote lircd server


       The  --permission  option  gives  the  file  permission of
       /dev/lircd if it has to be created  in  octal  representa­
       tion.   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  represen­
       tation).  If  /dev/lircd already exists this option has no

       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.

       With the --listen option you can let lircd listen for net­
       work  connections  on  the given port. The default port is
       by sending the HUP signal to the program. That way you can
       rotate old log files.


       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 con­
       nects 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


       The documentation for lirc is maintained  as  html  pages.
       They  are  located under html/ in the documentation direc­

lircd 0.6.6                October 2002                  LIRCD(1)



Security Code
Security Code
Type Security Code

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!

Amazon Wish List

Did You Know?
You can choose larger fonts by selecting a different themes.


Tell a Friend About Us

Bookmark and Share

Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.09 Seconds