Sophie

Sophie

distrib > Mandriva > 9.1 > ppc > by-pkgid > 1e83d3a59ba566dfa9bc2cd6aaa201ad > files > 25

lcdproc-0.4.3-2mdk.ppc.rpm

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML
><HEAD
><TITLE
>LCDproc Configuration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="LCDproc User's Guide"
HREF="book1.html"><LINK
REL="PREVIOUS"
TITLE="Generate And Install Packages of LCDproc"
HREF="x224.html"><LINK
REL="NEXT"
TITLE="The LCDproc Init Scripts"
HREF="x402.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>LCDproc User's Guide: The Ultimate Guide to LCDproc 0.4.3</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="x224.html"
ACCESSKEY="P"
>&#60;&#60;&#60; Previous</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="x402.html"
ACCESSKEY="N"
>Next &#62;&#62;&#62;</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="CONFIGURATION"
></A
>LCDproc Configuration</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="CONFIGURE-LCDD"
></A
>Configure LCDd</H1
><P
>As mentioned in the <A
HREF="c44.html"
>introduction</A
>
LCDd, the LCDproc server, now (with version 0.4.3 of LCDproc) has its
own configuration file, which is normally <TT
CLASS="FILENAME"
>/etc/LCDd.conf</TT
>.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you have not installed LCDproc from the sources the configuration
file might have a different location. You should find it when making
your system's package manager list all the files in the LCDproc package.</P
></TD
></TR
></TABLE
></DIV
><P
>The format of the <TT
CLASS="FILENAME"
>/etc/LCDd.conf</TT
> is ini-file-like.</P
><P
>It is divided into sections that start at
markers that look like [section]. Comments are all line-based comments,
and are lines that start with '#' or ';'.</P
><P
>The server has a 'central' section named [server]. Further each driver
has a section which defines how the driver acts. Those sections start with
[drivername].</P
><P
><A
NAME="WHICH-DRIVER"
></A
>The drivers are activated by specifiying them in a driver= line in the
server section, like:</P
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN269"
></A
><P
><B
>Example 1. <TT
CLASS="FILENAME"
>LCDd.conf</TT
>: Specify which driver to use</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>&#13;Driver=curses&#13;</PRE
></TD
></TR
></TABLE
></DIV
><P
>This tells LCDd to use the curses driver. The first driver specified here
that is capable of output functionality will be used as 'the' output driver.
All extra drivers can only serve as input.
The default driver to use is curses.</P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If LCDd is started automatically by an init-script using the curses driver
will lock <TT
CLASS="FILENAME"
>/dev/tty1</TT
>! So, be careful about what you are
doing here.</P
></TD
></TR
></TABLE
></DIV
><P
>The drivers can read their own options from the config file, but most of
them don't do this yet. They expect 'command-line'-format parameters that
were previously placed on the command line. These parameters can be
given to the driver in the following way:</P
><DIV
CLASS="EXAMPLE"
><A
NAME="AEN278"
></A
><P
><B
>Example 2. <TT
CLASS="FILENAME"
>LCDd.conf</TT
>: Compatibility mode for drivers written for 0.4.1</B
></P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>&#13;Arguments="place arguments here"&#13;</PRE
></TD
></TR
></TABLE
></DIV
><P
>The arguments between the quotes are passed to the driver.
As said before these are the same arguments that would have
been passed to the driver using the old command line format of</P
><P
><B
CLASS="COMMAND"
>LCDd -d driver "driverargs"</B
></P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The -d option still works, but does not allow driverargs any more.</P
><P
>If -d is specified on the command line, the Driver= options in the
config file are ignored.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="SERVER-SECTION"
></A
><TT
CLASS="FILENAME"
>LCDd.conf</TT
>: The [server] Section</H2
><P
>The [server] section of the <TT
CLASS="FILENAME"
>LCDd.conf</TT
> contains the
settings for the LCDproc server <TT
CLASS="APPLICATION"
>LCDd</TT
>.</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>Driver=</DT
><DD
><P
>Tells the server which driver(s) to use. See
<A
HREF="c254.html#WHICH-DRIVER"
>above</A
> for details</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The default setting is Driver=none which makes the server exit right
after the start. This is neccessary to avoid trouble with package installations.</P
></TD
></TR
></TABLE
></DIV
></DD
><DT
>Bind=</DT
><DD
><P
>Tells the server to bind to the given interface. Default to Bind=127.0.0.1 which
is actually the safest variant.</P
></DD
><DT
>Port=</DT
><DD
><P
>Tells the server to listen to this specified port; defaults to 13666.</P
></DD
><DT
>ReportLevel=</DT
><DD
><P
>Sets the reporting level; defaults to 2 (warnings and errors only).</P
></DD
><DT
>ReportToSyslog=</DT
><DD
><P
>Should we report to syslog instead of stderr ? Defaults to no.</P
></DD
><DT
>WaitTime=</DT
><DD
><P
>Sets the default time in seconds to display a screen.</P
></DD
><DT
>User=</DT
><DD
><P
>User to run as.  LCDd will drop its root privileges,
if any, and run as this user instead. Defaults to User=nobody.</P
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="90%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you want to use the server menu, to shutdown or reboot your system,
 you will have to set this to root. Otherwise LCDd does not have the
 privileges to run commands like <B
CLASS="COMMAND"
>init 6</B
>.</P
></TD
></TR
></TABLE
></DIV
></DD
><DT
>ServerScreen=</DT
><DD
><P
>Enables the server screen even when other screens are active. Defaults to
no.</P
></DD
><DT
>Foreground=</DT
><DD
><P
>The server will stay in the foreground if set to true.
Otherwise the server will fork to background and report
to syslog. Defaults to yes.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="INPUT-SECTION"
></A
><TT
CLASS="FILENAME"
>LCDd.conf</TT
>: The [input] Section</H2
><P
>The [input] section enables you to set some general ("global")
options related to the way <TT
CLASS="APPLICATION"
>LCDd</TT
> handles
input "events".</P
><DIV
CLASS="TABLE"
><A
NAME="AEN342"
></A
><P
><B
>Table 1. The Standard LCDd Input Keys</B
></P
><TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
CELLSPACING="0"
CELLPADDING="4"
CLASS="CALSTABLE"
><THEAD
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Keyname</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Function</TH
><TD
>&nbsp;</TD
></TR
><TR
><TH
ALIGN="LEFT"
VALIGN="TOP"
>&nbsp;</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Normal context</TH
><TH
ALIGN="LEFT"
VALIGN="TOP"
>Menu context</TH
></TR
></THEAD
><TBODY
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>PauseKey</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Pause/Continue</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Enter/select</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>BackKey</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Back (Go to previous screen)</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Up/Left</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>ForwardKey</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Forward (Go to next screen)</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Down/Right</TD
></TR
><TR
><TD
ALIGN="LEFT"
VALIGN="TOP"
>MainMenuKey</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Open main menu</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
>Exit/Cancel</TD
></TR
></TBODY
></TABLE
></DIV
><DIV
CLASS="NOTE"
><P
></P
><TABLE
CLASS="NOTE"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The way input keys are handled will change completely in LCDproc 0.5.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="FREEKEYOPTIONS"
></A
><TT
CLASS="FILENAME"
>LCDd.conf</TT
>: [input] Section: The Free*Key Options</H3
><P
>The Free*Key Options are interesting for those users whose keypad (or other input source)
has got only four (or less) keys. In this case LCDd would normally use all those
keys to enable you to control the server menu and the other server functions (like
switching to the next screen). If these keys are used by a client to do anything
but noticing that the user has e.g. entered the menu or switched to another screen,
this will probably cause trouble, as one keypress has several effects at the same
time.</P
><P
>The Free*Key options enable you to influence this behaviour.</P
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>FreePauseKey=</DT
><DD
><P
>If set to yes, this prevents LCDd from handling the PauseKey itself.
Then a client can request the key 'A' and handle it.</P
></DD
><DT
>FreeBackKey=</DT
><DD
><P
>If set to yes, this prevents LCDd from handling the BackKey itself.
Then a client can request the key 'B' and handle it.</P
></DD
><DT
>FreeForwardKey=</DT
><DD
><P
>If set to yes, this prevents LCDd from handling the ForwardKey itself.
Then a client can request the key 'C' and handle it.</P
></DD
><DT
>FreeMainMenuKey=</DT
><DD
><P
>If set to yes, this prevents LCDd from handling the MainMenuKey itself.
Then a client can request the key 'D' and handle it.</P
><DIV
CLASS="TIP"
><P
></P
><TABLE
CLASS="TIP"
WIDTH="90%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="./stylesheet-images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Even if you "free" the above keys, you can still use the menu
provided you set FreeMainMenuKey to no.</P
></TD
></TR
></TABLE
></DIV
></DD
></DL
></DIV
></DIV
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="DRIVERS-SECTION"
></A
><TT
CLASS="FILENAME"
>LCDd.conf</TT
>: The Drivers Section</H2
><P
>As mentioned earlier, each driver has its own section in the
<TT
CLASS="FILENAME"
>LCDd.conf</TT
>.</P
><P
>The settings are more or less self-explanatory. So, read through the
section of your driver and change everything neccessary.</P
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="x224.html"
ACCESSKEY="P"
>&#60;&#60;&#60; Previous</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="book1.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="x402.html"
ACCESSKEY="N"
>Next &#62;&#62;&#62;</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Generate And Install Packages of LCDproc</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The LCDproc Init Scripts</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>