|
|
397.
|
|
|
By default, LTSP5 encrypts the X session between the server. This makes your session more secure, but at the cost of increased processing power required on the thin client and on the server. If processing power is a concern to you, it's very easy to specify that the connection for either an individual workstation, or the default setting should use an unencrypted connection. To do so, simply specify:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:973(para)
|
|
|
404.
|
|
|
In this version of LTSP, there's a simple load-balancing solution implemented that allows administrators to have multiple Edubuntu servers on the network, and allow the thin client to pick which one of the servers it would like to log into.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1009(para)
|
|
|
405.
|
|
|
The host selection system is simple and flexible enough to allow administrators to implement their own policy on how they want the load balancing to happen: either on a random, load-based, or round robin system. See <xref linkend="multiple-server-setup"/> for details.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1014(para)
|
|
|
407.
|
|
|
There are several variables that one can define in the lts.conf file which control how the thin client interacts with the server. These are:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1024(para)
|
|
|
409.
|
|
|
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, it will be auto detected.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1034(para)
|
|
|
411.
|
|
|
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 'SERVER' parameter described above.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1048(para)
|
|
|
437.
|
|
|
<emphasis role="bold">sdm</emphasis>: Similar in functionality to ldm, but a little less graphically intensive.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1203(para)
|
|
|
446.
|
|
|
For the most part, LTSP does a very good job of detecting what hardware's on your thin client. However, it's possible that you may want to manually specify a kernel module to load after boot. Alternatively, you may have a script you've written that you've put in the chroot, and want to make sure gets run at startup. LTSP provides some hooks to allow you to do this.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:1276(para)
|
|
|
616.
|
|
|
Managing DHCP
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:2155(title)
|
