[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/Documentation/Stretch/HowTo/NetworkClients" by WolfgangSchweer

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianEdu/Documentation/Stretch/HowTo/NetworkClients" page has been changed by WolfgangSchweer:
https://wiki.debian.org/DebianEdu/Documentation/Stretch/HowTo/NetworkClients?action=diff&rev1=14&rev2=15

Comment:
various typo fixes / other improvements; thanks victory.

  }}}
  somewhere below the default settings.
  
- To force usage of a specific xserver on an LTSP client, set the {{{XSERVER}}} variable. For example:
+ To force the use of a specific xserver on an LTSP client, set the {{{XSERVER}}} variable. For example:
  
  {{{
  [192.168.0.11]
@@ -190, +190 @@

  ==== Part 1 ====
  It is possible to set up the clients to connect to one of several LTSP servers for load-balancing. This is done by providing `/opt/ltsp/i386/usr/share/ltsp/get_hosts` as a script printing one or more servers for LDM to connect to. In addition to this, each LTSP chroot needs to include the SSH host key for each of the servers.
  
- First of all, you must choose one LTSP server to be the load-balancing server. All the clients will PXE-boot from this server and load the Skolelinux image. After the image is loaded, LDM chooses which server to connect to by using the "get_hosts" script. How this is done you decide later on.
+ First of all, you must choose one LTSP server to be the load-balancing server. All the clients will PXE-boot from this server and load the Skolelinux image. After the image is loaded, LDM chooses which server to connect to by using the "get_hosts" script. You will decide later how this is done.
- 
+ .
  The load-balancing server must be announced to the clients as the "next-server" via DHCP. As DHCP configuration is in LDAP, modifications have to be done there. Use {{{ldapvi --ldap-conf -ZD '(cn=admin)'}}} to edit the appropriate entry in LDAP. (Enter the main server's root password at the prompt; if VISUAL isn't set, the default editor will be nano.)
  Search for a line reading {{{dhcpStatements: next-server tjener}}}
  Next-server should be the IP address or hostname of the server you chose to be the load-balancing server. If you use hostname you must have a working DNS. Remember to restart the DHCP service. 
@@ -200, +200 @@

  
  
  ==== Part 2 ====
- Now you have to make a "get_hosts" script that prints a server for LDM to connect to. The parameter LDM_SERVER overrides this script. In consequence, this parameter must not be defined if the get_hosts is going to be used. The get_hosts script writes on the standard output each server IP address or host name, in random order.
+ Now you have to make a "get_hosts" script which generates a list of server names for LDM to connect to. The parameter LDM_SERVER overrides this script. In consequence, this parameter must not be defined if the get_hosts is going to be used. The get_hosts script writes on the standard output each server IP address or host name, in random order.
  
  Edit "/opt/ltsp/i386/etc/lts.conf" and add something like this:
  
@@ -241, +241 @@

  
  LTSP diskless workstations handle audio locally and have none of the special setup needed for networked audio.
  
- === Use printers attachted to LTSP clients ===
+ === Use printers attached to LTSP clients ===
  
   * Attach the printer to the LTSP client machine (both USB and parallel port are supported). 
  
-  * Configure this machine to run a printer in lts.conf (default location: {{{/opt/ltsp/i386/etc/lts.conf}}}, see the LTSP manual {{{/usr/share/doc/ltsp/LTSPManual.html#printer}}} for details.
+  * Configure this machine to run a printer in lts.conf (default location: {{{/opt/ltsp/i386/etc/lts.conf}}}), see the LTSP manual {{{/usr/share/doc/ltsp/LTSPManual.html#printer}}} for details.
  
   *  Configure the printer using the web interface {{{https://www:631}}} on the main server; choose network printer type {{{AppSocket/HP JetDirect}}} (for all printers regardless of brand or model) and set {{{socket://<LTSP client ip>:9100}}} as connection URI.