A page in your DokuWiki was added or changed. Here are the details:

Date        : 2017/10/26 15:13
Browser     : Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 
Firefox/56.0
IP-Address  : 78.43.91.217
Hostname    : HSI-KBW-078-043-091-217.hsi4.kabel-badenwuerttemberg.de
Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1509024329
New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: Added explanation on how to use session names with blanks
User        : stefanbaur

@@ -740,9 +740,9 @@
   * ''ldap1=ldap-backupserver-1.example.com:389'' - this allows you to specify 
the first of up to two LDAP backup servers when using LDAP authentication
* ''ldap2=ldap-backupserver-2.example.com:389'' - this allows you to specify the second of up to two LDAP backup servers when using LDAP authentication * ''nodpms'' - Will not touch DPMS settings at all (by default, ''blank=0'' does both ''xset s off'' and ''xset -dpms''). Use this along with
''blank=n'' if you do want to blank the screen, but your screen is confused by 
DPMS settings.
   * 
''pubkey=tftp|http|https|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.authorized_keys''
 - Allows you to add an ssh public key file to the ThinClient, so your 
administrators can log in remotely using SSH. Note that this file needs to be 
chmodded 644, not 600, on the web server.  **Attention: Whoever manages to 
spoof this server name will have root access to your ThinClients. Using HTTPS 
will mitigate this - an attacker would not only have to spoof the server name, 
but also the matching certificate.**
-   *  ''session=sessionname'' - use this to specify a session by name that 
should be pre-selected on startup. The name must be listed in the sessions file 
and may only contain characters from the following charset: //a-zA-Z0-9.:/ _-// 
(We suggest naming the default session ''default'' and using 
''session=default''.) As of 2017-10-26, this feature is only available in builds
created from the https://github.com/LinuxHaus/live-build-x2go::feature/openbox 
repository/branch. The official repository will follow soon (or so we hope ;-)).
+   *  ''session=sessionname'' - use this to specify a session by name that should be 
pre-selected on startup. The name must be listed in the sessions file and may only 
contain characters from the following charset: //a-zA-Z0-9.:/ _-// (We suggest naming the 
default session ''default'' and using ''session=default''.) When using a session name 
with blanks, please enclose the sessionname in either single or double quotes, like so: 
''session="session name"'' / ''session='session name''' As of 2017-10-26, this 
feature is only available in builds created from the 
https://github.com/LinuxHaus/live-build-x2go::feature/openbox repository/branch. The 
official repository will follow soon (or so we hope ;-)).
   * ''tcpprint'' - Will allow you to use local LPT/USB printers like "dumb" 
network printers (listening to port 9100 and above).
Requires MAC->IP mapping in DHCP server (and optionally, DNS->IP mapping), or static IPs - else your print jobs will end up on random devices. This setup is preferred over the X2GoClient's built-in printing for locally attached printers if X2GoServer and ThinClients are on the same network. It is not recommended when your X2Go connection goes across the internet or when the ThinClient is actually a laptop roaming between different networks. **Attention:** When used without ''tcpprintonlyfrom'' (see below), this means anyone that can reach your thin client via e.g. ping can also send print jobs to it! * ''tcpprintonlyfrom=x.x.x.x'' - Will allow you to specify which IP address may connect to Port 9100 and above for printing to a locally attached LPT/USB printer. This should be the IP of your CUPS server or whatever print server system you use. Understands the same syntax as xinetd's ''only_from''. * ''xinerama=left-of|right-of|above|below|same-as'' - Allows you to specify
how multiple screens are handled (same-as clones the primary screen to all secondary 
screens, the other commands will cascade and thus expand the screen). Note that the 
current implementation will enforce "same-as" if it detects a touch screen 
driver (wacom) and no other pointing device. This is so you won't get stuck being unable 
to log off, for example, due to your touch device being limited to one screen.
   * ''xorg-resolution=HRESxVRES'' - will force the horizontal resolution to 
HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'', 
useful if autodetection for the correct screen size fails, but you do get as 
far as seeing the X2Go GUI


--
This mail was generated by DokuWiki at
https://wiki.x2go.org/

_______________________________________________
x2go-commits mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-commits

Reply via email to