ltsp-docs 1.2-1 / usr / share / gnome / help / ltsp / C / lts.conf.xml

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<refentry id="lts.conf" revision="0.1">
  <refentryinfo>
    <date>2008-11-18</date>
  </refentryinfo>

  <refmeta>
    <refentrytitle>lts.conf</refentrytitle>

    <manvolnum>5</manvolnum>

    <refmiscinfo class="manual">File Formats and Conversions</refmiscinfo>

    <refmiscinfo class="source">LTSP</refmiscinfo>

    <refmiscinfo class="version">5</refmiscinfo>
  </refmeta>

  <refnamediv id="lts-conf-name">
    <refname>lts.conf</refname>

    <refpurpose>Main configuration file for LTSP</refpurpose>
  </refnamediv>

  <!-- body begins here -->

  <refsynopsisdiv id="lts-conf-synopsis">
    <para>Any line beginning with a '#' is considered a comment. Options are
    of the format:</para>

    <synopsis>VARIABLE=value</synopsis>
  </refsynopsisdiv>

  <refsect1>
    <title>Description</title>

    <para>This file gets parsed when LTSP client starts up. The section
    defined by [default] gets applied to all clients, unless there is a
    specification for a particular client that overrides it. The per-client
    specs are prefixed by [&lt;mac address&gt;]</para>

    <para>You may also name an arbitrary section with a name, with settings
    underneath that section. You may then inherit that section with the
    <varname>LIKE</varname> variable. The Example section has an illustration
    of this.</para>

    <para>boolean values are specified by 'Y,y,True,true' for true and
    'N,n,False,false' for false</para>
  </refsect1>

  <refsect1 id="lts-conf-general">
    <title>lts.conf - general parameters</title>

    <variablelist id="lts-conf-general-list">
      <varlistentry>
        <term><varname>CONFIGURE_FSTAB</varname></term>

        <listitem>
          <para>boolean, default <emphasis>True</emphasis></para>

          <para>/etc/fstab is generated by boot scripts</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>FSTAB_0..FSTAB_9</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Complete lines to add to /etc/fstab, for example:<screen>
FSTAB_1="server:/home    /home           nfs     defaults,nolock 0       0"
 </screen></para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>CRONTAB_01..CRONTAB_10</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A crontab line to add for a thin client.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>DNS_SERVER</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>A valid IP for domain name server Used to build the client's
          resolv.conf file. Not needed by default.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SEARCH_DOMAIN</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>sets a valid search domain in the clients's resolv.conf file.
          Used to build the resolv.conf file. Not needed by default.</para>

          <para>Needed if <varname>DNS_SERVER</varname> is set</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>HOSTNAME</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This parameter sets the host name for the thin client, for
          situations when if no DNS is available. A hostname is auto-generated
          if no hostname is set.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>HOSTNAME_BASE</varname></term>

        <listitem>
          <para>string, default <emphasis>ltsp</emphasis></para>

          <para>This parameter sets the base for the autogenerated host name
          for the thin client.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>HOSTNAME_EXTRA</varname></term>

        <listitem>
          <para>string, default <emphasis>ip</emphasis></para>

          <para>This parameter determines weather autogenerated host names are
          appended with information based on the ip address or mac address.
          Values are "ip" or "mac".</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>NBD_SWAP</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Set this to <command>True</command> if you want to turn on NBD
          swap.</para>

          <para>If unspecified, it's automatically enabled for thin clients
          with less than 300 MB RAM and for fat clients with less than 800 MB
          RAM.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>NBD_SWAP_PORT</varname></term>

        <listitem>
          <para>integer, default <emphasis>10809</emphasis></para>

          <para>The port on which NBD swapping will occur. An nbd-server
          export named <varname>swap</varname> is normally used.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>NBD_SWAP_SERVER</varname></term>

        <listitem>
          <para>IP address, default <emphasis>SERVER</emphasis></para>

          <para>The NBD swap server can exist on any server on the network
          that is capable of handling it. You can specify the IP address of
          that server. The default is whatever the value of
          <varname>SERVER</varname> set to.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>NBD_SWAP_THRESHOLD</varname></term>

        <listitem>
          <para>integer, default <emphasis>300</emphasis></para>

          <para>Automatically enable <varname>NBD_SWAP</varname> if the client
          has less RAM than the specified. For FAT clients, it defaults to
          800.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>RM_SYSTEM_SERVICES</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A space separated list of services that shouldn't start on the
          clients even if they're installed, for example:<screen>RM_SYSTEM_SERVICES="apache2 dnsmasq mysql nbd-server nfs-kernel-server"</screen></para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>RM_THIN_SYSTEM_SERVICES</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Same as <varname>RM_SYSTEM_SERVICES</varname>, but it only
          affects thin clients.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>KEEP_SYSTEM_SERVICES</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Some services are deleted by default when an LTSP client
          boots, either to save RAM, or because they don't make sense for
          netbooted machines. If you need some of them you can list them in
          <varname>KEEP_SYSTEM_SERVICES</varname>, for example:<screen>KEEP_SYSTEM_SERVICES="acpid avahi-daemon bluetooth cups"</screen></para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SERVER</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>This is the server that is used for the
          <varname>XDM_SERVER</varname>, <varname>TELNET_HOST</varname>,
          <varname>XFS_SERVER</varname> and <varname>SYSLOG_HOST</varname>, if
          any of those are not specified explicitly. If you have one machine
          that is acting as the server for everything, then you can just
          specify the address here and omit the other server parameters. If
          this value is not set, it will be auto detected as the machine that
          the thin client booted from.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SYSLOG_HOST</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>If you want to send logging messages to a machine other than
          the default server, then you can specify the machine here. If this
          parameter is NOT specified, then it will use the
          <varname>SERVER</varname> parameter described above. Starting from
          LTSP 5.4.1 and on, this parameter must be specified to enable remote
          logging.</para>

          <para>You have to configure your server to accept remote logging as
          well.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>USE_LOCAL_SWAP</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>If you have a hard drive installed in the thin client, with a
          valid swap partition on it, this parameter will allow the thin
          client to swap to the local hard drive.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>TIMEZONE</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>The timezone code for the thin client to use.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>TIMESERVER</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>The address of an NTP time server that the thin client can set
          it's time from. If unset, the thin client just uses the BIOS
          time.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SHUTDOWN_TIME</varname></term>

        <listitem>
          <para>string, format hh:mm:ss in 24 hour format, default
          <emphasis>unset</emphasis></para>

          <para>Time at which thin client will automatically shut down.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LTSP_FATCLIENT</varname></term>

        <listitem>
          <para>boolean, default <emphasis>unset</emphasis></para>

          <para>Enable Fat Client support. It's automatically enabled if any
          sessions exist in /usr/share/xsessions.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>FAT_RAM_THRESHOLD</varname></term>

        <listitem>
          <para>integer, default <emphasis>300</emphasis></para>

          <para>Disable fat client support if less RAM is present.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-localdev">
    <title>lts.conf - local devices</title>

    <variablelist id="lts-conf-localdev-list">
      <varlistentry>
        <term><varname>LOCALDEV</varname></term>

        <listitem>
          <para>boolean, default <emphasis>True</emphasis></para>

          <para>This parameter enables local devices support, like CD's and
          USB sticks. Users plugging them in should see them on the desktop,
          after they've been allowed to access the FUSE subsystem on the
          server. Check your distibutions docs to see how this is done on your
          distribution.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCALDEV_DENY_CD</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>This parameter disables local device support for CD and
          DVD-rom devices.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCALDEV_DENY_FLOPPY</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>This parameter disables local device support for floppy
          devices.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCALDEV_DENY_INTERNAL_DISKS</varname></term>

        <listitem>
          <para>boolean, default <emphasis>True</emphasis></para>

          <para>This parameter disables local device support for internal ATA
          and SCSI hard disk devices.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCALDEV_DENY_USB</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>This parameter disables local device support for USB
          devices.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCALDEV_DENY</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This parameter disables local device support for devices
          matching certain patterns. Values are specified as a comma-separated
          list of sysfs attributes, which can be obtained by using udevadm
          info (or udevinfo). for example: <screen>
                        udevadm info -q env -n /dev/hda
                        ID_TYPE=disk
                        ID_BUS=ata
                        </screen> should return a list of the attributes
          relevent to /dev/hda. to exclude this disk and disks like it using
          LOCALDEV_DENY: LOCALDEV_DENY="ID_BUS:ata+ID_TYPE:disk" would match
          devices that were on the ata bus that were disks.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-modules">
    <title>lts.conf - scripts and modules</title>

    <variablelist id="lts-conf-modules-list">
      <varlistentry>
        <term><varname>MODULE_01...MODULE_10</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Up to 10 kernel modules can be loaded by using these
          configuration entries. The entire command line that you would use
          when running insmod can be specified here. For example:</para>

          <screen>
MODULE_01 = uart401.o
MODULE_02 = "sb.o io=0x220 irq=5 dma=1"
MODULE_03 = opl3.o
                    </screen>

          <para>If the value of this parameter is an absolute path name, then
          <command>insmod</command> will be used to load the module.
          Otherwise, <command>modprobe</command> will be used.</para>

          <para>In normal circumstances, you shouldn't need to specify
          anything here, as most hardware will be auto-detected.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>RCFILE_01...RCFILE_10</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Commands to be executed from
          <filename>/etc/rc.local</filename> when the client boots.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-printer">
    <title>lts.conf - printer parameters</title>

    <variablelist id="lts-conf-printer-list">
      <varlistentry>
        <term><varname>PRINTER_0_DEVICE</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>The device name of the printer. Valid device names such as
          <filename>/dev/lp0</filename>, or <filename>/dev/usblp0</filename>
          are allowed.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_PORT</varname></term>

        <listitem>
          <para>integer, default <emphasis>9100</emphasis></para>

          <para>The TCP/IP Port number to use for the print server.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_TYPE</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Can either be set to P (for parallel), U (for USB) or S (for
          serial). Autodetected in most cases (except for serial).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_WRITE_ONLY</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Some parallel printers may need this set in order for the thin
          client to communicate to them properly. If you have problems with a
          parallel printer only printing part of the print job, try setting
          this to <emphasis>True</emphasis>.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_SPEED</varname></term>

        <listitem>
          <para>integer, default <emphasis>9600</emphasis></para>

          <para>Should be set to the baud rate of the printer (serial printers
          only).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_FLOWCTRL</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Should be set to the flow control desired for the printer
          (serial printers only).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_PARITY</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Specifies whether parity should be enabled for the printer
          (serial printers only).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_DATABITS</varname></term>

        <listitem>
          <para>integer, default <emphasis>8</emphasis></para>

          <para>Specifies how many data bits for the printer (serial printers
          only).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PRINTER_0_OPTIONS</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Specifies specific options for the printer (serial printers
          only).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_PRINTER_LIST</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Comma separated list of printers that will be displayed for
          that thin client (requires patched cups, included in Debian and
          Ubuntu).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_PRINTER_DEFAULT</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Default printer for the thin client.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SCANNER</varname></term>

        <listitem>
          <para>boolean, default <emphasis>unset</emphasis></para>

          <para>This parameter enables scanners for the thin client.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-keyboard">
    <title>lts.conf - keyboard parameters</title>

    <variablelist id="lts-conf-keyboard-list">
      <varlistentry>
        <term><varname>CONSOLE_KEYMAP</varname></term>

        <listitem>
          <para>string, default <emphasis>en</emphasis></para>

          <para>A valid console keymap. Allows you to specify a valid console
          keymap for TELNET_HOST sessions.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XKBLAYOUT</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid xkb layout. Consult the X.org documentation for valid
          settings.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XKBMODEL</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid xkb model. Consult the X.org documentation for valid
          settings.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XKBVARIANT</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid xkb variant. Consult the X.org documentation for valid
          settings.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XKBRULES</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid xkb rules specifier. Consult the X.org documentation
          for valid settings.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XKBOPTIONS</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid xkb options specifier. Consult the X.org documentation
          for valid settings.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-touchscreen">
    <title>lts.conf touchscreen parameters</title>

    <variablelist id="lts-conf-touchscreen-list">
      <varlistentry>
        <term><varname>USE_TOUCH</varname></term>

        <listitem>
          <para>Enable touchscreen</para>

          <para>default &lt;unset&gt;, Enable touchscreen</para>

          <informaltable frame="none">
            <tgroup cols="4">
              <tbody>
                <row>
                  <entry>X_TOUCH_DEVICE</entry>

                  <entry>Path to device</entry>

                  <entry>/dev/ttyS0</entry>

                  <entry>set device for touchscreen</entry>
                </row>

                <row>
                  <entry>X_TOUCH_DRIVER</entry>

                  <entry>Touchscreen driver</entry>

                  <entry>elographics</entry>

                  <entry>set driver for touchscreen</entry>
                </row>

                <row>
                  <entry>X_TOUCH_MAXX</entry>

                  <entry>integer</entry>

                  <entry>3588</entry>

                  <entry>Xmax</entry>
                </row>

                <row>
                  <entry>X_TOUCH_MAXY</entry>

                  <entry>integer</entry>

                  <entry>3526</entry>

                  <entry>Ymax</entry>
                </row>

                <row>
                  <entry>X_TOUCH_MINX</entry>

                  <entry>integer</entry>

                  <entry>433</entry>

                  <entry>Xmin</entry>
                </row>

                <row>
                  <entry>X_TOUCH_MINY</entry>

                  <entry>integer</entry>

                  <entry>569</entry>

                  <entry>Ymin</entry>
                </row>

                <row>
                  <entry>X_TOUCH_UNDELAY</entry>

                  <entry>integer</entry>

                  <entry>10</entry>

                  <entry>Untouch delay</entry>
                </row>

                <row>
                  <entry>X_TOUCH_RTPDELAY</entry>

                  <entry>integer</entry>

                  <entry>10</entry>

                  <entry>Repeat touch delay</entry>
                </row>
              </tbody>
            </tgroup>
          </informaltable>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-sound">
    <title>Sound and volume control parameters</title>

    <para>These parameters allow you to control the volume on the thin
    client.</para>

    <variablelist id="lts-conf-sound-list">
      <varlistentry>
        <term><varname>SOUND</varname></term>

        <listitem>
          <para>boolean, default <emphasis>True</emphasis></para>

          <para>This parameter enables sound for the thin client.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SOUND_DAEMON</varname></term>

        <listitem>
          <para>string, default <emphasis>pulse</emphasis></para>

          <para>This parameter sets which sound daemon to use on the thin
          client. Values are esd, nasd, and pulse (default).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>VOLUME</varname></term>

        <listitem>
          <para>integer, default <emphasis>90</emphasis></para>

          <para>This represents an integer percentage of the volume, ranging
          from 0 to 100%.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>HEADPHONE_VOLUME</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>This represents an integer percentage of the headphone volume,
          ranging from 0 to 100%.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>PCM_VOLUME</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>This represents an integer percentage of the PCM volume,
          ranging from 0 to 100%.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>CD_VOLUME</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>This represents an integer percentage of the CD input volume,
          ranging from 0 to 100%.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>FRONT_VOLUME</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>This represents an integer percentage of the front speaker
          volume, ranging from 0 to 100%.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>MIC_VOLUME</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>This represents an integer percentage of the microphone input
          volume, ranging from 0 to 100%.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-xorg">
    <title>lts.conf - Xorg parameters</title>

    <para>These parameters affect how Xorg behaves.</para>

    <variablelist id="lts-conf-xorg-list">
      <varlistentry>
        <term><varname>USE_XFS</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Instructs the thin client to look at the
          <varname>XFS_SERVER</varname> option, and use XFS for serving
          fonts.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XFS_SERVER</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>If you are using an X Font Server to serve fonts, then you can
          use this entry to specify the IP address of the host that is acting
          as the font server. If this is not specified, it will use the
          default server, which is specified with the
          <varname>SERVER</varname> entry described above.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>CONFIGURE_X</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>If you want to be able to configure the individual settings of
          the X configuration file, without having the X automatically
          configure the graphics card for you, you must enable this option. By
          default this option is turned off. To turn it on do: <screen>CONFIGURE_X = True</screen>You
          don't need this option just for keyboard and mouse settings. It
          corresponds to the graphic card and monitor options only.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_CONF</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>If you want to create your own complete X.org config file, you
          can do so and place it in the
          <filename>/opt/ltsp/&lt;arch&gt;/etc/X11</filename> directory. Then,
          whatever you decide to call it needs to be entered as a value for
          this configuration variable. For example: X_CONF =
          /etc/X11/my-custom-xorg.conf Note that for the thin client, you
          reference it from <filename>/etc/X11</filename>.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_RAMPERC</varname></term>

        <listitem>
          <para>integer, default <emphasis>100</emphasis></para>

          <para>Percentage of RAM for X server. Some programs allocate a large
          amount of ram in the X.org server running on your thin client.
          Programs like <command>Firefox</command> and
          <command>Evince</command> can use up so much ram, that they
          eventually exhaust all your physical ram, and NBD swap, causing your
          thin client to crash. If you find your clients being booted back to
          a login prompt, or freezing up when viewing certain PDF's or web
          pages, this may be the problem.</para>

          <para>The <varname>X_RAMPERC</varname> variable stands for X RAM
          PERCent, and is a number between 0 and 100 that specifies how much
          of the free space on your thin client X.org is allowed to consume.
          You'll generally want to set it at something lower than 100 percent,
          if you're having problems. Experimentation has shown a value between
          80 and 90 will usually keep the terminal alive. What will then
          happen is the program consuming the memory will die, as opposed to
          the thin client itself. If you're having unexplained terminal
          problems, specifying:</para>

          <para>X_RAMPERC = 80</para>

          <para>in your <filename>lts.conf</filename> file may improve
          things.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_VIRTUAL</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>If you want to have a virtual screen which is larger than the
          physical screen on your thin client, you would configure that by
          providing a string of the form "width height" in this parameter,
          similar to the <filename>xorg.conf</filename> format.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XDM_SERVER</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>If you're using the older <command>startx</command> screen
          script, and need to specify a different XDMCP server, then you can
          specify the server here. If this parameter is NOT specified, then it
          will use the <varname>SERVER</varname> parameter described
          above.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XSERVER</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>You can use this parameter to override which X server the thin
          client will run. For PCI and AGP video cards, this parameter should
          not be required. The thin client should normally be able to
          auto-detect the card.</para>

          <para>If, for some reason you do need to manually set it, here are
          some valid values:</para>

          <para>ark, ati, atimisc, chips, cirrus_alpine cirrus, cirrus_laguna,
          cyrix, dummy, fbdev fglrx, glint, i128, i740, i810, imstt, mga,
          neomagic, newport, nsc, nv, r128, radeon, rendition, riva128, s3,
          s3virge, savage, siliconmotion, sis, sisusb, tdfx, tga, trident,
          tseng, v4l, vesa, vga, via, vmware, voodoo</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_MOUSE_DEVICE</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This is the device node that the mouse is connected to. If it
          is a serial mouse, this would be a serial port, such as
          <filename>/dev/ttyS0</filename> or <filename>/dev/ttyS1</filename>.
          This is not needed for PS/2 or USB mice, as they are
          auto-detected.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_MOUSE_PROTOCOL</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Should be auto-detected. However, valid entries
          include:</para>

          <para>sunkbd, lkkbd, vsxxxaa, spaceorb, spaceball, magellan,
          warrior, stinger, mousesystems, sunmouse, microsoft, mshack,
          mouseman, intellimouse, mmwheel, iforce, h3600ts, stowawaykbd,
          ps2serkbd, twiddler, twiddlerjoy</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_MOUSE_EMULATE3BTN</varname></term>

        <listitem>
          <para>boolean, default <emphasis>unset</emphasis></para>

          <para>Normally unset, may need to be set to <emphasis>Y</emphasis>
          for certain 2 button mice.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_NUMLOCK</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>If this variable is set to <emphasis>True</emphasis>, then the
          numlock key will be defaulted to on when the terminal boots. Note
          that the <command>numlockx</command> command must be installed in
          the chroot for this to work.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_COLOR_DEPTH</varname></term>

        <listitem>
          <para>Integer, default <emphasis>unset</emphasis></para>

          <para>This is the number of bits to use for the colour depth.
          Possible values are <command>8</command>, <command>16</command>,
          <command>24</command> and <command>32</command>. 8 bits will give
          256 colours, 16 will give 65536 colours, 24 will give 16 million
          colours and 32 bits will give 4.2 billion colours! Not all X servers
          support all of these values. The default for thin clients is 16 in
          order to minimize network bandwidth, while for fat clients the X
          server default is used.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_SMART_COLOR_DEPTH</varname></term>

        <listitem>
          <para>boolean, default <emphasis>True</emphasis></para>

          <para>If set, thin clients no longer default to 16 bit colour depth
          but use the X server default instead.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_HORZSYNC</varname></term>

        <listitem>
          <para>min-max, default <emphasis>unset</emphasis></para>

          <para>This sets the X.org <command>HorizSync</command> configuration
          parameter. This should be auto-detected for your monitor, however,
          if you want to force a lower resolution, use this parameter to do
          so.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_VERTREFRESH</varname></term>

        <listitem>
          <para>min-max, default <emphasis>unset</emphasis></para>

          <para>This sets the X.org <command>VertRefresh</command>
          configuration parameter. This should be auto-detected for your
          monitor. If you need to force a lower resolution, use this parameter
          to do so.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_VIDEO_RAM</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This sets the X.org <command>VideoRam</command> configuration
          parameter. The setting is in kilobytes. This should be auto-detected
          for your monitor. If you need to force a different video ram
          setting, use this parameter to do so.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_OPTION_01...X_OPTION_12</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid Device option. This allows you to specify
          <command>Option</command> settings in the
          <filename>xorg.conf</filename> file, to add options to the video
          driver. A common use for this will be to test turning off
          acceleration in your driver, if you're having trouble. An example
          usage would be:</para>

          <screen>
X_OPTION_01 = "\"NoAccel\"" X_OPTION_02 = "\"AnotherOption\" \"True\""
                    </screen>

          <para>You probably won't need these except in special
          circumstances.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_MONITOR_OPTION_01...X_MONITOR_OPTION_10</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>A valid Monitor option, that would normally be used in an
          xorg.conf file.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_MODE_0...X_MODE_2</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>These set the X.org <varname>ModeLine</varname> configuration.
          For example, if your thin client comes up in a higher resolution
          than what you want, say, 1280x1024, specifying:</para>

          <screen>
X_MODE_0 = 1024x768
                    </screen>

          <para>should get your desired resolution on startup.</para>

          <para>X_MODE_* require XRANDR_DISABLE=True to work. For drivers that
          support XRANDR, the XRANDR_MODE_* variabled are preferred. See the
          XRANDR section.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>X_BLANKING</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>When set, <varname>X_BLANKING</varname> will cause DPMS
          standby to activate after the number of seconds provided. If the
          monitor does not support DPMS, then the blanking screensaver will
          activate. If <varname>X_BLANKING</varname> is set to 0, the monitor
          will remain on indefinitely. NOTE: This does not apply to the
          <command>xdmcp</command> or <command>startx</command> screen script.
          Also, server-side Xclients such as power managers and screensavers
          may override this setting.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-xrandr">
    <title>lts.conf options - XRANDR options</title>

    <variablelist id="lts-conf-xrandr-list">
      <varlistentry>
        <term><varname>XRANDR_COMMAND_0 ... XRANDR_COMMAND_9</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Full xrandr command to run when X starts. They're useful to
          define and add custom modes, for example:<screen>
XRANDR_COMMAND_0="xrandr --newmode 1024x600 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync"
XRANDR_COMMAND_1="xrandr --addmode VGA1 1024x600"
XRANDR_COMMAND_2="xrandr --output VGA1 --mode 1024x600"
 </screen>You can use <command>cvt</command> to find the correct timings for
          new modes.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_DISABLE</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Disables XRANDR output handling so that the older
          <varname>X_MODE_0</varname> way of setting resolution works. This is
          useful on older Xorg drivers that don't support XRANDR.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_OUTPUT_0 ... XRANDR_OUTPUT_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Define xrandr output - can also be used for multihead
          positioning</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_MODE_0 ... XRANDR_MODE_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Valid video mode resolution. Sets mode for corresponding
          output.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_NEWMODE_0 ... XRANDR_NEWMODE_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Specifies a valid modeline for a corresponding output.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_RATE_0 ... XRANDR_RATE_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Sets refresh rate for the corresponding output.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_DPI_0 ... XRANDR_DPI_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Sets the DPI for the corresponding output.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_ROTATE_0 ... XRANDR_ROTATE_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Sets the rotation for the corresponding output.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_REFLECT_0 ... XRANDR_REFLECT_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Sets the reflection for the corresponding output.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_SIZE_0 ... XRANDR_SIZE_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Sets the resolution for the corresponding output (for xrandr
          &lt;1.2).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>XRANDR_ORIENTATION_0 ...
        XRANDR_ORIENTATION_8</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Sets the orientation for the corresponding output (for xrandr
          &lt;1.2).</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-screen">
    <title>lts.conf options - screen scripts</title>

    <variablelist id="lts-conf-screen-list">
      <varlistentry>
        <term><varname>SCREEN_01...SCREEN_12</varname></term>

        <listitem>
          <para>string, default <emphasis>ldm</emphasis></para>

          <para>Up to 12 screen scripts can be specified for a thin client.
          This will give you up to 12 sessions on the thin client, each
          accessible by pressing the Ctrl-Alt-F1 through Ctrl-Alt-F12
          keys.</para>

          <para>Currently, possible values include: kiosk, ldm, menu, rdesktop
          (deprecated), shell, ssh, startx (deprecated), telnet, xdmcp,
          xfreerdp, xterm</para>

          <para>Look in the
          <filename>$CHROOT/usr/share/ltsp/screen.d</filename> directory for
          more scripts, or write your own, and put them there.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>TELNET_HOST</varname></term>

        <listitem>
          <para>IP address, default <emphasis>unset</emphasis></para>

          <para>If the thin client is setup to have a character based
          interface, then the value of this parameter will be used as the host
          to telnet into. If this value is NOT set, then it will use the value
          of <varname>SERVER</varname> above.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-ldm">
    <title>lts.conf options - LDM options</title>

    <variablelist id="lts-conf-ldm-list">
      <varlistentry>
        <term><varname>LDM_AUTOLOGIN</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>This option allows the thin client to login automatically
          without the need for a username and password. To set it set <screen>LDM_AUTOLOGIN = True</screen>
          for the corresponding thin client. This will attempt to log in the
          thin client with username = hostname and password = hostname. You
          can also set a user and password with
          <varname>LDM_USERNAME</varname> and <varname>LDM_PASSWORD</varname>
          variables.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_DEBUG_TERMINAL</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Opens a local terminal after login for debugging
          purposes.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_DIRECTX</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>This is arguably the most important LDM option, as it allows
          you to turn off the encrypted X tunnel via SSH, and instead run a
          less secure, but much faster unencrypted tunnel. Users who have
          slower thin clients will want to set this to
          <emphasis>True</emphasis>. It is set to <emphasis>True</emphasis> by
          default in Fedora.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_GUESTLOGIN</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>This option places a GUEST LOGIN button underneath the entry
          field for username and password. To set it set <screen>LDM_GUESTLOGIN = True</screen>
          for the corresponding thin client. You can also set a user and
          password with <screen>LDM_USERNAME = John</screen> and <screen>LDM_PASSWORD = secret</screen>,
          although not setting these will default to the hostname of the thin
          client.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_GUEST_SERVER</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This is a space-separated list of available servers where
          guest logins are available. The first server in the list will be the
          default guest login server unless the user selects another from the
          preferences menu at login time.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_USER_ALLOW</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This option allows you to give access to certain thin clients
          based on the username set in <filename>/etc/passwd</filename>. For
          example, thin client A should only be used by Jane, Bob, and Fred,
          while thin client B is to be used by Harry only. By adding these
          options to the corresponding mac addresses you allow or deny access
          to the thin clients in question. Example:</para>

          <screen>
[thin:client:A:mac:address]
LDM_USER_ALLOW = Jane,Bob,Fred
[thin:client:B:mac:adddress]
LDM_USER_ALLOW = Harry
                   </screen>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_LOGIN_TIMEOUT</varname></term>

        <listitem>
          <para>integer</para>

          <para>This lets LDM automatically login after the set amount of time
          in seconds. If you specify this option, then do not specify
          LDM_AUTOLOGIN. Use it in this format:</para>

          <screen>
[thin:client:mac:address]
LDM_LOGIN_TIMEOUT = 25
                    </screen>

          <para>Note that you will need to also set LDM_GUESTLOGIN=True for
          LDM_LOGIN_TIMEOUT to be useful.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_USERNAME</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This is the username that LDM will use for autologin.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_PASSWORD</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This is the password that LDM will use for autologin.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_SYSLOG</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Normally, LDM logs to a simple file on the thin client, namely
          <filename>/var/log/ldm.log</filename>. This has the advantage of
          being fast, but the disadvantage of being hard to read for the
          administrator in the event of a problem, as the administrator must
          either spawn a shell screen session, or enable root login in tty1.
          By setting this option to "True", you can log up to the server
          <emphasis>if you've enabled your server's syslog for remote
          logging.</emphasis></para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_SERVER</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This is a space-separated list of available servers for LDM to
          log into. The first server in the list will be the default server
          unless the user selects another from the preferences menu at login
          time.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_LANGUAGE</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This allows the system administrator to override the default
          locale settings on the server by setting the environment variables
          LANG, LANGUAGE and LC_ALL at login.</para>

          <para>Use the LANG variable to set the default locale for LDM's user
          interface.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_FORCE_LANGUAGE</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Same as <varname>LDM_LANGUAGE</varname>, but it overrides any
          previously user selected language and it even hides the LDM language
          selection menu.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_SSHOPTIONS</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Allows you to specify custom options to the ssh sessions
          started between LDM and the server.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SSH_OVERRIDE_PORT</varname></term>

        <listitem>
          <para>integer, default <emphasis>unset</emphasis></para>

          <para>If you run your ssh server different from the defult, you may
          set the port the thin client will use with this parameter.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>SSH_FOLLOW_SYMLINKS</varname></term>

        <listitem>
          <para>boolean, default <emphasis>unset</emphasis></para>

          <para>Causes <filename>sshfs</filename> mounted filesystems for
          local applications to follow symlinks. By default it's false for
          symlinks under $HOME and true for any
          <varname>LOCAL_APPS_EXTRAMOUNTS</varname>.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_SESSION</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Used to chose the default session on the server, for
          example:<screen>
LDM_SESSION="gnome-fallback"
 </screen>You can find the list of services that your server provides in
          <filename>/usr/share/xsessions</filename>.</para>

          <para>If the user has selected a specific session though LDM or
          another DM in the past, that's stored in his
          <filename>~/.dmrc</filename>, and it overrides the default
          session.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_FORCE_SESSION</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Same as <varname>LDM_SESSION</varname>, but it overrides any
          previously selected sessions by the user and it even hides the LDM
          session selection menu.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_XSESSION</varname></term>

        <listitem>
          <para>string, default <emphasis>Xsession</emphasis></para>

          <para>Allows you to specify custom script on the server for LDM to
          run, rather than the server's standard script for starting an X
          session (usually <command>Xsession</command>).</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_LIMIT_ONE_SESSION</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Only allow a given user to log into one thin-client at a
          time.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_LIMIT_ONE_SESSION_PROMPT</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Prompt to kill processes of other logins when other logins are
          detected. Requires LDM_LIMIT_ONE_SESSION to be set.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LDM_THEME</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Specify the name of the LDM theme. It can reference a
          directory in /usr/share/ldm/themes, or be specified as a full path
          to the theme dir (both relative to the chroot).</para>

          <para>To use the theme in
          <filename>/opt/ltsp/i386/usr/share/ldm/themes/MYTHEME</filename>,
          you'd specify:</para>

          <screen>
LDM_THEME=MYTHEME
                    </screen>

          <para>In your <filename>lts.conf</filename> file.</para>

          <para>Alternately, To use the theme in
          <filename>/opt/ltsp/i386/etc/MYTHEME</filename>, you'd
          specify:</para>

          <screen>
LDM_THEME=/etc/MYTHEME
                    </screen>

          <para>In your <filename>lts.conf</filename> file.</para>
        </listitem>
      </varlistentry>
      
      <varlistentry>
        <term><varname>LDM_PASSWORD_HASH</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>When set to <emphasis>True</emphasis>, this will create a proper 
          shadow entry on the client, allowing for screen locking, and other 
          things which require authentication to work. Note, this allows you to
          change your password locally, or possibly other actions such as sudo, but
          these changes are only temporary and will not persist on reboot.</para>

          <para>versions: LDM 2.2.14+, LTSP 5.5.2+</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-localapps">
    <title>Local Applications</title>

    <variablelist id="lts-conf-localapps-list">
      <varlistentry>
        <term><varname>LOCAL_APPS</varname></term>

        <listitem>
          <para>boolean, default <emphasis>True</emphasis></para>

          <para>Enables support for running local apps on the thin
          client.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCAL_APPS_EXTRAMOUNTS</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This parameter enables extra mount points to be mounted on the
          thin client with sshfs. This require a commas separated list of
          directory.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCAL_APPS_MENU</varname></term>

        <listitem>
          <para>boolean, default <emphasis>False</emphasis></para>

          <para>Enables overriding of menu items from remote (server)
          applications. If this is set to <emphasis>True</emphasis>, local
          applications in the users menu will be used instead of the
          applications on the server.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCAL_APPS_MENU_ITEMS</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>This item should contain a comma separated list of application
          names as they appear on their .desktop files.</para>
        </listitem>
      </varlistentry>

      <varlistentry>
        <term><varname>LOCAL_APPS_WHITELIST</varname></term>

        <listitem>
          <para>string, default <emphasis>unset</emphasis></para>

          <para>Used to allow only specified space-separated commands to be
          run as local apps, allow all is default if unset. Full-paths are
          required for each command. No spaces in the names are
          allowed.</para>
        </listitem>
      </varlistentry>
    </variablelist>
  </refsect1>

  <refsect1 id="lts-conf-samples">
    <title>Samples</title>

    <refsect2 id="k12ltsp">
      <title>K12LTSP</title>

      <para><programlisting id="lts.conf-sample">
# Global defaults for all clients
# if you refer to the local server, just use the
# "server" keyword as value
# see lts_parameters.txt for valid values
################
[default]
    #X_COLOR_DEPTH=16
    LOCALDEV=True
    SOUND=True
    NBD_SWAP=True
    SYSLOG_HOST=server
    #XKBLAYOUT=de
    SCREEN_02=shell
    SCREEN_03=shell
    SCREEN_04=shell
    SCREEN_05=shell
    SCREEN_06=shell
    SCREEN_07=ldm
    # LDM_DIRECTX=True allows greater scalability and performance
    # Turn this off if you want greater security instead.
    LDM_DIRECTX=True
    # LDM_SYSLOG=True writes to server's syslog
    LDM_SYSLOG=True


################
# A setting stanza for an old machine
################
[oldmachine]
    X_COLOR_DEPTH=8
    X_MODE_0=800x600

################
# Example of the LIKE variable
################
[01:23:DE:AD:BE:EF]
    LIKE=oldmachine
    SCREEN_02=shell

################
#[MAC ADDRESS]: Per thin client settings
################
[00:11:25:84:CE:BA]
    XSERVER = vesa
    X_MOUSE_DEVICE=/dev/ttyS0
    X_MOUSE_PROTOCOL=intellimouse

###############
# A Thin Client Print server
# (switch off X by pointing tty7 to shell,
# to save resources)
###############
[00:11:25:93:CF:00]
    PRINTER_0_DEVICE=/dev/usblp0
    SCREEN_07=shell

###############
# A workstation that executes a specific
# command after login
###############
[00:11:25:93:CF:02]
    LDM_SESSION=/usr/bin/myloginscript
                </programlisting></para>
    </refsect2>
  </refsect1>

  <refsect1 id="lts-conf-notes">
    <title>NOTES</title>

    <para>When using NBD to export the client image (the default in Ubuntu),
    lts.conf is fetched via TFTP, so lts.conf should go in the TFTP directory,
    for example <filename>dvar/lib/tftpboot/ltsp/i386/lts.conf</filename>. For
    distributions that use NFS, the traditional lts.conf place is
    <filename>/opt/ltsp/i386/etc/lts.conf</filename>, although in recent
    versions it can be fetched via TFTP as well.</para>
  </refsect1>

  <refsect1 id="lts-conf-see-also">
    <title>SEE ALSO</title>

    <para>Other manpage references go here...</para>
  </refsect1>
</refentry>