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

Date        : 2016/12/15 03:37
Browser     : Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 
Firefox/45.0
IP-Address  : 78.43.90.159
Hostname    : HSI-KBW-078-043-090-159.hsi4.kabel-badenwuerttemberg.de
Old Revision: http://wiki.x2go.org/doku.php/doc:howto:tce?rev=1481772904
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment] User : stefanbaur

@@ -183,9 +183,9 @@
   * ''noroot'' - do not allow the local user account on the ThinClient (named 
"user") to become root, e.g. using sudo **always set this unless you are 
debugging an image and need to log in locally**
   * ''nouser'' - do not allow the local user account on the ThinClient (named "user") to 
log in at the console or remotely (using password "live") **always set this unless you 
are debugging an image and need to log in locally**
   *
''sessionsurl=http://your-http-server-ip-here/x2go-demo/x2go-tce.sessions'' - 
use this to specify a sessions file. You need this unless you are using a 
session broker. See below how to add this file to your HTTP or FTP server.
   * ''broker-url=ssh:<nowiki>//</nowiki>your-broker-address-here'' - this 
allows you to specify an X2Go Session Broker instead of a sessions file (not limited to an 
ssh-based broker, works with an http-based broker as well)
-   * 
''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - 
this allows you to add a ssh public key file to the ThinClient, so your 
administrators can log in remotely using SSH
+   * 
''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - 
this allows you to add an ssh public key file to the ThinClient, so your 
administrators can log in remotely using SSH
   * 
''xorgconfurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.xorg.conf'' - 
when a client outright refuses to boot into the
graphical X2Go login screen, but gets stuck at the console or a black screen 
instead, yet you can get the GUI to work using a regular Linux on the same 
hardware, you can disable the X Server's autodetection and force it to use the 
xorg.conf specified here.  Note that you should use a more descriptive name for 
the file, as described below.
   * ''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
   * ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this 
allows you to specify an LDAP server to authenticate against
   * ''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


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

_______________________________________________
x2go-commits mailing list
x2go-commits@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-commits

Reply via email to