A page in your DokuWiki was added or changed. Here are the details:
Date : 2016/12/15 03:11
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=1481770844
New Revision: http://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [Building your own netbootable X2Go-TCE image]
User : stefanbaur
@@ -177,17 +177,30 @@
</file>
=== What options are available under FURTHER-OPTIONS-GO-HERE? ===
- * sessionsurl=http://your-http-server-ip-here/x2go-demo/x2go-tce.sessions
+ * ''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.
+ * ''pubkey=http://192.168.1.1/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
+ * ''xorg-resolution=HRESxVRES'' - will force the horizontal resolution to
HRES and the vertical resolution to VRES, e.g. ''xorg-resolution=1280x1024'',
useful if autodetection fails
+ * ''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
- === Adding the session configuration file to your HTTP or FTP Server ===
+
+ === 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
* copy it to x2go-tce.sessions
* using an editor of your choice, edit x2go-tce.sessions so it contains only
the sessions you want to appear on the ThinClient, and none that might have
been created earlier.
* log on to your HTTP or FTP server and change to the x2go-tce directory in
your webroot/ftproot.
* copy the x2go-tce.sessions file with your desired configuration to this
directory.
+ === Adding the x2go-tce.authorized_keys keyfile to your HTTP or FTP Server ===
+ Again, this is assuming you already have an existing, working HTTP or FTP
server setup.
+ * locate your current
authorized_keys file - it should be at ~/.ssh/authorized_keys
+ * copy it to x2go-tce.authorized_keys
+ * using an editor of your choice, edit x2go-tce.authorized_keys so it
contains only the keys you want to appear on the ThinClient, and none that
might have been created for a different purpose.
+ * log on to your HTTP or FTP server and change to the x2go-tce directory in
your webroot/ftproot.
+ * copy the x2go-tce.authorized_keys file with your desired configuration to
this directory.
--
This mail was generated by DokuWiki at
http://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
http://lists.x2go.org/listinfo/x2go-commits
