[X2Go-Commits] [[X2Go Wiki]] page changed: doc:howto:tce

[wiki-admin at x2go.org]

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

Date        : 2016/12/16 18:50
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=1481903029
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Setting up your own netbootable X2Go-TCE environment] 
User        : stefanbaur

@@ -179,21 +179,22 @@
  
  === What options are available under FURTHER-OPTIONS-GO-HERE? ===
  
  These two are mutually exclusive, i.e. never put both of them in the same config:
-   * ''sessionsurl=http://your-http-server-ip-here/x2go-tce/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below for how to add this file to your HTTP or FTP server.
+   *
''sessionsurl=http://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.sessions'' - use this to specify a sessions file. You need this unless you are using a session broker. See below for 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)
  
  These are entirely optional:
-   * ''pubkey=http://your-http-server-ip-here/x2go-tce/x2go-tce.authorized_keys'' - //not yet implemented// this will allow 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.
    * ''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
-   * ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow 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)
    * ''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
    * ''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 
    * ''updateurl=rsync|http|ftp://your-http-server-ip-or-dns-here/path-to-update-files'' - //not yet implemented//. Will allow you to update an image in the background when using local storage instead of PXE. Download task will start at a randomized interval to avoid unintentional dDOSing of the update server/network infrastructure. The updater will even work when using NTFS for local storage, but only if the //toram// boot option is used.
    * ''bwlimit=nn%'' - //not yet implemented//. Will allow you to specify a bandwidth limit for the backgrounded update task.
+   * ''pubkey=tftp|http|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce.authorized_keys'' - //not yet implemented// this will allow 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.
+   * ''xinerama=left-of|right-of|above|below|same-as'' - //not yet implemented//. Will allow 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)
+ 
  === Required unless using the X2Go Session Broker: Adding the x2go-tce.sessions session configuration file to your HTTP or FTP Server ===
  Again, this is assuming you already have an existing, working HTTP or FTP server setup.
    * run X2GoClient on any computer you like, and configure a session the same way it should appear on the ThinClient <note tip>when using a Windows client, run x2goclient.exe --portable, or it will store the session information in the registry, rather than in a "sessions" file.</note>
    * locate the "sessions" file you just created - it should
be at ~/.x2goclient/sessions


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