Skip to topic | Skip to bottom
Home

Ltsp
Ltsp.LtsConfr1.11 - 06 Oct 2006 - 00:10 - LloydHazletttopic end

Start of topic | Skip to actions

lts.conf

This is the client configuration file. It usually resides in /opt/ltsp/i386/etc/lts.conf

The lts.conf file is made of "sections". That is, there can be a default section called '[default]'. There can also be sections for each individual workstation. Entries in the specific workstation sections take precedence over entries in the default section. The workstation can be identified by hostname, IP address or MAC address. That is, if ws004 has an IP address of 192.168.0.4 and a MAC address of 00:50:56:59:7F:81, it can be specified by any of the following:

    [ws004]

      -OR-

    [192.168.0.4]

      -OR-

    [00:50:56:59:7F:81]

Case is NOT important. 'ws004' is equivelant to 'WS004'.

The lts.conf file supports the ability to define groups of workstations, or to say that one workstation "inherits" the same settings as another workstation.

Let's say that you have 3 different types of machines that all need special settings. We'll create 3 groups, called DELL, Compaq and HP

We can create groups as follows:

[Default]
   SERVER           = 192.168.0.254
   X_MOUSE_DEVICE   = /dev/psaux
   X_MOUSE_PROTOCOL = Auto

[DELL]
   XSERVER          = ati
   X_MOUSE_DEVICE   = /dev/ttyS0
   X_MOUSE_PROTOCOL = "Microsoft"

[Compaq]
   XSERVER          = sis

[HP]
   XSERVER          = cirrus_alpine
   X_MOUSE_DEVICE   = /dev/input/mice


[ws001]
   LIKE             = DELL
   X_MOUSE_PROTOCOL = "Logitech"

[ws002]  LIKE       = DELL
[ws003]  LIKE       = DELL

[ws006]  LIKE       = Compaq   
[ws007]  LIKE       = Compaq   

[ws012]  LIKE       = HP
[ws013]  LIKE       = HP
[ws014]  LIKE       = HP

In the example above, I showed with ws001 that you can set it to inherit all of the settings from DELL, but then override the X_MOUSE_PROTOCOL attribute (or any other attribute)


Here's the list of available settings:

General Settings

SERVER = 192.168.0.254

This is the server that is used for the XDM_SERVER, TELNET_HOST, XFS_SERVER and SYSLOG_HOST 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, 192.168.0.254 will be used.

SYSLOG_HOST

If you want to send logging messages to a machine other than the default server, then you can specify the IP address of the machine here. If this parameter is NOT specified, then it will default to the value of the 'SERVER' parameter described above.

TELNET_HOST

If the workstation 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 the SERVER parameter above.

TELNET_SESSIONS

This setting will determine how many telnet sessions to run. Each session will be on a separate virtual screen, accessable by using Alt-F1 through Alt-Fn.

DNS_SERVER

Used to build the resolv.conf file. If this parameter is NOT set, then it will use the value of the SERVER parameter above.

SEARCH_DOMAIN

Used to build the resolv.conf file.

MODULE_01 through MODULE_10

Upto 10 kernel modules can be loaded by using these configuration entries. The simplest way to load a module is to specify the module name only (e.g. rtl8129), which will be loaded by modprobe. Alternatively, the entire command line that you would enter when running insmod may be used instead. For example, the following lines would use insmod:

         MODULE_01 = agpgart.o
         MODULE_02 = uart401.o
         MODULE_03 = "sb.o io=0x220 irq=5 dma=1"
         MODULE_04 = opl3.o

Note that the full path to a module may need to be specified if using insmod (e.g. /lib/modules/2.6.17.3-ltsp-1/kernel/drivers/net/rtl1839.o), and that kernel 2.4 modules use a '.o' suffix whilst 2.6 modules use '.ko'.

RAMDISK_SIZE

When the workstation boots, it creates a ramdisk and mounts it on the /tmp directory. You can control the size of the filesystem with this parameter. Specify it in units of kbytes (1024 bytes). To create a ramdisk size of 2 megabytes, specify RAMDISK_SIZE = 2048. If you change the size of the ramdisk here, you will also need to change the size of the ramdisk within the kernel. This can be compiled in, or if you are using Etherboot or Netboot, you can tell the kernel the ramdisk size when you tag the kernel with mknbi-linux. You can also tell the kernel the size of the ramdisk in the dhcpd.conf file with option-129. The default value for the RAMDISK_SIZE is 1024 ( 1 mb ).

NFS_SERVER

For Local apps, additional filesystems are mounted. You can specify the IP address of the server that contains those filesystems. If this is not specified, it will default to the value of 'SERVER'

USE_NFS_SWAP

This option is used in LTSP-4.1 and earlier. If you want to let the workstation swap via NFS, set this to 'Y'. This can be useful when the workstation has a very low amount of memory (like 8mb). if not specified, it will default to 'N'.

USE_NBD_SWAP

This option is used in LTSP-4.2 and later. If you want to let the workstation swap via NBD, set this to 'Y'. This can be useful when the workstation has a very low amount of memory (like 8mb). if not specified, it will default to 'N'.

SWAP_SERVER

If you do enable USE_NFS_SWAP (in LTSP-4.1 and earlier) or USE_NBD_SWAP (in LTSP-4.2 and later), you can specify the IP address of the NFS or NBD server that will serve up the swap file. If this is not specified, it will use the value of NFS_SERVER.

NFS_SWAPDIR

This specifies the directory on the swap server, where the swapfiles are to be stored. If not specified, it will default to "/var/opt/ltsp". This option has no effect in LTSP-4.2 and later (see Swapping over NBD to specify the swap directory).

SWAPFILE_SIZE

If you have enabled swapping via NFS, you can specify the size of the swapfile with this parameter. If you change this value, then the next time the workstation is booted, the swapfile will automatically be resized. if this parameter is not specified, it will default to 64m. This option has no effect in LTSP-4.2 and later (see Swapping over NBD to set the size of the swapfile).

RCFILE_01 through RCFILE_10

Upto 10 additional RC scripts can be specified. They will be run during the bootup process of the workstation. This is a handy "hook" for adding functionality to the workstation.

SOUND

If you have the sound package installed, you can set this parameter to 'Y' to enable sound on each workstation. If not specified, this defaults to 'N'.

XINETD_SERVICES

Introduced in LTSP-4.2. A list of services that can be started on the workstation using xinetd. Currently, "saned" is the only option, and is used to connect a scanner to a workstation.

X Related settings

XDM_SERVER

If you want to point XDM to a machine other than the default server, then you can specify the server here. If this parameter is NOT specified, then it will use the 'SERVER' paramter described above.

XSERVER

This defines which X server the workstation will run. Normally, you can leave ommit this field and the Video card will be Automatically detected.

For XFree86 4.x, you can specify the driver module. X4 drivers such as ati, cirrus, s3virge, sis and more can be specified. XFree86 3.3.6, you specify the Xserver. Such as XF86_SVGA, XF86_S3, etc. See the page VideoCards for a complete list of available modules.

if this parameter is not specified, then 'auto' will be used, and the video chipset will automatically be detected.

DISABLE_ACCESS_CONTROL

Normally, only programs running on the server are allowed to display their windows on the workstation. If you have additional servers, where you want to run X programs from, you can use the xhost command to add each additional server to the list of allowed servers. Or, you can disable access control by setting this option to "Y". CAUTION! This can create a security problem, because any user can run a program that displays on any users desktop.

X_MODE_0 through X_MODE_2

This is how you can specify either the screen resolution or a complete modeline for the workstation. There are formats for this value. Either just a resolution, or a resolution followed by a complete modeline. For example, if you want to use a built-in modeline, but set the resolution to 800 x 600, you can specify:

        X_MODE_0  = 800x600

If you want to specify a complete modeline, you can specify it like this:

        X_MODE_0 = 800x600 40 800 840 968 1056 600 601 605 628 +hsync +vsync

If the X_MODE_x entries are not specified, then the built-in resolutions and modelines will be used.

X_DEVICE_OPTION_01 through X_DEVICE_OPTION_10

Upto 10 device options can be specified for the video device. This is useful if the video chipset requires additional options to function properly.

X4_MODULE_01 through X4_MODULE_10

Upto 10 additional modules can be loaded for XFree86 4.x.

X4_BUSID

Some motherboard chipsets don't properly recognize the video chipset so you need to explicitly tell XFree86 which bus the video card is on. Particularly if you are using VMware as a client. For VMware, set the value to 'PCI:0:15:0'. If this parameter is not specified, then it is not used.

X4_DRI

If you want to run X4's Direct Rendering, you can specify the module you want to load

X_VIDEORAM

Some video chipsets don't properly report the amount of video ram that is onboard the video card. This can be a problem, expecially on Intel i810 chipsets with 32mb of main system ram. The value is in kbytes. So, for an i810 based system, you could specify:

          X_VIDEORAM = 2048

If this parameter is not specified, then the Xserver will attempt to probe the chipset for the amount of video ram.

X_MOUSE_PROTOCOL

Any value that will work for the XFree86 Pointer Protocol keyword can be put here. Typical values include "Microsoft", "PS/2" and "IMPS/2". The default value for this is "PS/2" but you should probably try "auto" (recent addition to X.org and XFree86).

X_MOUSE_DEVICE

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 /dev/ttyS0 or /dev/ttyS1. If it is a PS/2 keyboard mouse, this value would be /dev/psaux. The default value for this is /dev/psaux.

X_MOUSE_RESOLUTION

This is the 'Resolution' value in the XF86Config file. A typical value for a serial mouse is 50 and a typical value for a PS/2 mouse is 400. The default value for this is 400.

X_MOUSE_BUTTONS

This tells the system how many buttons the mouse has. Usually set to 2 or 3. The default value for this is 3.

X_MOUSE_EMULATE3BTN

If this is set to 'Y', it will set the 'Emulate3Buttons' option in the XF86Config file. This is for when you have a 2-button mouse and you want it to emulate a 3-button mouse by pressing both buttons at the same time.

X_MOUSE_BAUD

For serial mice, this defines the baud rate. The default value is 1200.

X_COLOR_DEPTH

This is the number of bits to use for the color depth. Possible values are 8, 15, 16, 24 and 32. 8 bits will give 256 colors, 16 will give 65536 colors, 24 will give 16 million colors and 32 bits will give 4.2 billion colors! Not all X servers support all of these values. The default value is 16.

USE_XFS

You have a choice of running the X Font Server (XFS) or reading the fonts through the NFS filesystem. The font server should provide a simple way of keeping all of the fonts in one place, but there has been some problems when the number of workstations grows past about 40. The 2 values for this option are 'Y' and 'N'. The default is 'N'. If you do want to use a font server, then you can use the XFS_SERVER parameter to specify which host will act as the font server.

XFS_SERVER

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 SERVER parameter described above.

X_HORZSYNC

This sets the XFree86 HorizSync? configuration parameter. It defaults to "31-62".

X_VERTREFRESH

This sets the XFree86 VertRefresh? configuration parameter. It defaults to "55-90".

XF86CONFIG_FILE

If you want to create your own complete XF86Config file, you can do so and place it in the /opt/ltsp-4.1/i386/etc directory. Then, whatever you decide to call it needs to be entered as a value for this configuration variable. For example:

        XF86CONFIG_FILE = XF86Config.ws004

USE_TOUCH

If you are connecting a touch screen to the workstation, you can enable it by setting this entry to Y. If enabled, additional configuration entries will configure specific aspects of the touch screen. The default value is N. The only touch screens that are proven to work are from EloTouch? (http://www.elotouch.com)

X_TOUCH_DEVICE

A touch screen works like a mouse and usually is interfaced with the workstation through a serial port. You can specify which serial port with this entry. For example, you could set it to /dev/ttyS0. There is no default value for this entry.

X_TOUCH_MINX

Calibration entry for an EloTouch? touch screen. Defaults to 433.

X_TOUCH_MAXX

Calibration entry for an EloTouch? touch screen. Defaults to 3588.

X_TOUCH_MINY

Calibration entry for an EloTouch? touch screen. Defaults to 569.

X_TOUCH_MAXY

Calibration entry for an EloTouch? touch screen. Defaults to 3526.

X_TOUCH_UNDELAY

Calibration entry for an EloTouch? touch screen. Defaults to 10.

X_TOUCH_RPTDELAY

Calibration entry for an EloTouch? touch screen. Defaults to 10.

LOCAL_APPS

If you want the ability to run applications locally on a workstation, set this variable to Y. Several additional steps must be taken on the server to enable local apps. See the 'Local Apps' section in the LTSP manual for more information. The default value is N.

NIS_DOMAIN

If you do setup LOCAL_APPS, then you need to have an NIS server on the network. The NIS_DOMAIN entry is where you specify the NIS domain name. It needs to match a domain name that has been defined on the NIS server. This is NOT the same thing as an internet DOMAIN. The default value is 'ltsp'.

NIS_SERVER

Normally, NIS will do a broadcast to look for an NIS server on the network. If you want to specify a certain server as being the NIS server, then you can enter the IP address of that server here.

Keyboard parameters

There are several keyboard configuration parameters within XFree86. We have provided access to the paramters from within the lts.conf file. If you specify a parameter in lts.conf, then it will be used in the XF86Config file that is generated. Refer to the XFree86 documentation for more information on the meaning of the parameters.

XkbTypes

The default value is the word 'default'.

XkbCompat?

The default value is the word 'default'.

XkbSymbols?

The default value is 'us(pc101)'.

XkbModel?

The default value for this is 'pc101'.

XkbLayout

The default value for this is 'us'.

Printer configuration parameters

Upto three printers can be connected to a diskless workstation. A combination of serial and parallel printers can be configured via the following entries in the lts.conf file:

PRINTER_0_DEVICE

The device name of the first printer. Names such as /dev/usb/lp0, /dev/lp0, /dev/ttyS0, or /dev/ttyS1 are allowed.

PRINTER_0_TYPE

The type of the printer. Valid choices are 'U' for USB, 'P' for Parallel, and 'S' for serial.

PRINTER_0_PORT

The TCP/IP Port number to use. By default, it will use 9100.

PRINTER_0_SPEED

If the printer is serial, this is the setting that will select the baud rate. By default, 9600 will be used.

PRINTER_0_FLOWCTRL

For serial printers, the flow control can be specified. Either 'S' for Softwre (XON/XOFF) flow control, or 'H' for Hardware (CTS/RTS) flow control. If neither is specified, 'S' will be used.

PRINTER_0_PARITY

For serial printers, the parity can be specified. The choices are: 'E'-Even, 'O'-Odd or 'N'-None. If not specified, 'N' will be used.

PRINTER_0_DATABITS

For serial printers, the number of data bits can be specified. The choices are: '5', '6', '7' and '8'. If not specified, '8' will be used.

PRINTER_0_WRITE_ONLY

Some printers will detect that the port is read-write, and expect to be able to send feedback. Setting the port to WRITE-ONLY will make it so that the printer doesn't detect that. If not specified 'N' will be used.

Settings for a 2nd printer. See the descriptions for the first printer.

  PRINTER_1_DEVICE
  PRINTER_1_TYPE
  PRINTER_1_PORT       Defaults to 9101
  PRINTER_1_SPEED
  PRINTER_1_FLOWCTRL
  PRINTER_1_PARITY
  PRINTER_1_DATABITS
  PRINTER_1_WRITE_ONLY

Settings for a 3rd printer. See the descriptions for the first printer.

  PRINTER_2_DEVICE
  PRINTER_2_TYPE
  PRINTER_2_PORT       Defaults to 9102
  PRINTER_2_SPEED
  PRINTER_2_FLOWCTRL
  PRINTER_2_PARITY
  PRINTER_2_DATABITS
  PRINTER_2_WRITE_ONLY

Issues in this page

The following keys are not documented but should be:

  • SCREEN_##
  • HOTPLUG
  • LOCAL_STORAGE
  • X_USBMOUSE_DEVICE, X_USBMOUSE_PROTOCOL, and others in i386/etc/build_x4_cfg
  • X_XINERAMA in i386/etc/build_x4_cfg
  • X_SCREEN_POS in i386/etc/build_x4_cfg
  • VOLUME, MIC_VOLUME, CD_VOLUME in i386/etc/rc.sound
  • SNMP_* in i386/etc/rc.snmpd

to top

You are here: Ltsp > ManIndex > LtsConf

to top

Copyright © 1999-2006 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback