Man Linux: Main Page and Category List


       ledd.conf - configuration file for the LED control daemon


       The  file ledd.conf is the default configuration file for ledd(5), part
       of the ledcontrol package. It contains information about on which  TTYs
       the  LEDs  are  set,  logging  options, pipes and startup programs. The
       default configuration file should be adequate for most and it  is  very
       well  commented  itself, so it should be easy to configure ledd just by
       looking at the file.

       The file consists of lines with a keyword  and  options,  separated  by
       whitespaces.  Leading  spaces on lines are ignored, and blank lines and
       lines whose first nonblank character  is  a  number  sign  (‘‘#’’)  are


       tty TTY (default: none)
              Set  the LEDs on TTY. Several TTYs can be specified, each on its
              own line. It is recommended that only /dev/console is  used,  as
              having others is known to cause problems in X.

       fixtty TTY (default: none)
              On  exit  set  the  LEDs on TTY to reflect the real Lock states.
              This option may contain shell  wildcards  and  you  can  specify
              several  patterns,  each on its own line. It is not necessary to
              correct the LEDs on the TTY on which X is on.  (The  reason  why
              this  has a separate option is explained in the file PROBLEMS in
              the ledcontrol distribution.)

       daemon [TRUE|FALSE] (default: FALSE)
              Will ledd fork into the background on startup. This  option  can
              be overriden on the command line.

       log TYPE (default: syslog/stderr)
              Where  does  ledd  log  messages.  Possible  values  of TYPE are
              "syslog"  for  logging  via  syslogd(8),  "stderr"  for  writing
              messages  to  standard  error  and  "none"  for  no logging. The
              default is "syslog" if available, otherwise "stderr".

       pipefile FILE (default: none)
              Create a pipe FILE and read commands from it. It is created with
              660 permissions (owner and group have read/write). Several pipes
              can be defined, each on its own line. More pipes can be  defined
              on the command line.

       startup FILE (default: none)
              Execute  FILE  at  startup  and  read commands from its standard
              output. Everything it prints on standard error is  logged  on  a
              warning  level.  Several  files  can be defined, each on its own
              line, and the line may contain  command  line  options  for  the
              program.  More  startup  programs  can be defined on the command

       pidfile FILE (default: none)
              Store process ID in FILE while running.  It  is  suggested  that
              this  is  kept  at  /var/run/  Only one PID file can be
              defined and it can be overriden on the command line.


       # Set LED on any console you’re on.
       # It is suggested only /dev/console is used.
       tty /dev/console

       # Fix LEDs on TTYs 1 through 6 (a Linux box often has 6 text consoles)
       fixtty /dev/tty[1-6]

       # Use ledd as a daemon
       daemon TRUE

       # Log error messages, warnings and notices via syslogd(8)
       log syslog

       # Read commands from /var/run/ledd-pipe
       pipefile /var/run/ledd-pipe

       # Read commands from the default startup script
       startup /usr/share/ledcontrol/

       # Store PID in /var/run/ Use of this is recommended.
       pidfile /var/run/


              default configuration file for ledd

              location of the default startup script

              configuration file for


       ledd(8),, ledcontrol.conf(5), ledcontrol(1)


       Ledcontrol was written by Sampo Niskanen  <>.  You
       can     get     the     latest     version     of    ledcontrol    from