|
|
371.
|
|
|
Using a squashfs image we can now merge that together in a unionfs to get writeable access which is a lot faster during bootup.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:782(para)
|
|
|
372.
|
|
|
A squashed root filesystem uses less network bandwidth.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:787(para)
|
|
|
373.
|
|
|
Many users and administrators have asked us to eliminate NFS, for reasons of site policy. Since the squashed image is now served out by <command>nbd-server</command>, which is an entirely userspace program, and is started as the user nobody, this should help to eliminate concerns over NFS shares.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:791(para)
|
|
|
388.
|
|
|
We'll go over the <filename>lts.conf</filename> entries you'll need to control these features below.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:916(para)
|
|
|
389.
|
|
|
To help understand the following sections, a bit of an explanation of how <command>ldm</command> does it's work is needed. Most thin client display managers tend to run up on the server. The <command>ldm</command> display manager is unique in that it runs on the thin client itself. This allows the thin client to have a lot of choice as to how it will set up the connection. A typical login session goes as follows:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:921(para)
|
|
|
393.
|
|
|
Now, the users selected session is started via the master socket. Depending on whether or not an encrypted connection has been requested, via the LDM_DIRECTX parameter, the session is either connected back to the local display via the ssh tunnel, or via a regular TCP/IP connection.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:950(para)
|
|
|
394.
|
|
|
During the session, any memory sticks, or other local devices that are plugged in, communicate their status to the server via the ssh control socket.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:958(para)
|
|
|
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)
|
|
|
399.
|
|
|
in your <filename>lts.conf</filename> file in the appropriate stanza.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:983(para)
|
|
|
401.
|
|
|
This new version of LDM supports auto login of accounts, if specified in the <filename>lts.conf</filename> file. Simply create a config stanza for each of the terminals you want to log in automatically (you can use either MAC address, IP address, or hostname) and specify the variable <command>LDM_USERNAME</command> and <command>LDM_PASSWORD</command>. Note that you must have created these accounts on the server, with the passwords specified. An example will serve to illustrate how to use this:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
handbook/C/server.xml:988(para)
|
