A page in your DokuWiki was added or changed. Here are the details:
Date : 2019/01/17 18:23
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:52.9) Gecko/20100101
Goanna/3.4 Firefox/52.9 PaleMoon/27.9.4
IP-Address : 149.172.203.221
Hostname : HSI-KBW-149-172-203-221.hsi13.kabel-badenwuerttemberg.de
Old Revision: https://wiki.x2go.org/doku.php/doc:howto:tce?rev=1547747737
New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [What options are available under FURTHER-OPTIONS-GO-HERE?] added
lots of new options that are now available via the latest buildscripts on github
User : stefanbaur
@@ -885,10 +885,11 @@
* ''blank=n|n:n:n'' - Will disable (''blank=0'') or set screensaver timeout.
Use ''blank=n:n:n'' to set DPMS Standby/Suspend/Off values. Standby value
equals screensaver timeout value. All values are given in seconds.
* ''blankdpmsfix'' - This forces the TFT do black for a few seconds during
the X startup phase, then forces it back on
again. This fixes an occasional "black screen" issue that occurs with some
flaky client/TFT hardware combinations when using DisplayPort connectors, and could
otherwise only be remediated by manually turning the TFT off and back on again. (feature
available via github repo, soon via x2go repo too)
*
''branding=https|http|ftp://your-http-server-ip-or-dns-here/x2go-tce/x2go-tce-branding.svg''
- use this to specify an SVG file to "brand" your X2Go-TCE with. It will
replace the seal icon in the lower left of the login screen. See below for how to add
this file to your HTTP, HTTPS, or FTP server. **Attention: Whoever manages to spoof the
server name can inject rogue images into your ThinClients.** To mitigate this risk, use
HTTPS, where the attacker would have to spoof both server name and matching certificate.
* ''copysecring'' - this will scan for USB media and fixed disk media (with
USB media taking precedence) at boot for one or more of the following
directories:
''config/ssh'', 'ssh', ''.ssh''. The volume must be labeled ''X2GO-TCE-LIVE''
or ''PORTABLEAPP'' and may use any supported file system. Any SSH Secret Keys
found there will be copied into ''/home/user/.ssh'' (in the ramdisk), with
proper permissions and ownerships for the default user account. This may come
in handy when you are using SSH Secret Keys on USB media, but need to log in
and out of sessions often, and don't want to leave the USB media plugged in all
the time/don't want to have to re-insert it before each session startup.
**Attention: This poses a security risk when other people are using your
ThinClient afterwards (as they will have access to your keys).** To mitigate
this risk,be sure to power-cycle the ThinClient once you are done. You
//should// specify this parameter when booting X2Go-TCE-Live from portable
media when you want to use SSH Secret Keys, to make sure your secret key on the
FAT/NTFS partition is available. But as stated above, be sure to power-cycle the
machine once you're done.
- * ''earlyblankdpmsfix'' - This forces the TFT do black for a few seconds during the
initial boot phase (right after the squashfs was downloaded), then forces it back on
again. This fixes an occasional "black screen" issue that occurs with some
flaky client/TFT hardware combinations when using DisplayPort connectors, and could
otherwise only be remediated by manually turning the TFT off and back on again. (feature
available via github repo, soon via x2go repo too)
+ * ''earlyblankdpmsfix'' - This forces the TFT do black for a few seconds during the
initial boot phase (right after the squashfs was downloaded), then forces it back on
again. This fixes an occasional "black screen" issue that occurs with some
flaky client/TFT hardware combinations when using DisplayPort connectors, and could
otherwise only be remediated by manually turning the TFT off and back on again.
Earlyblankdpmsfix can also be called as ''earlyblankdpmsfix=nnnn'', where ''nnnn'' is
the blanking time in milliseconds (so, ''earlyblankdpmsfix=1500'' equals 1.5
seconds). (feature available via github repo, soon via x2go repo too)
* ''homepageurl="URL1[|URL2|URLn]"'' - this is only available in MiniDesktop mode. It allows you
to specify one or more web pages that show up on Browser start/when clicking the "Home" icon. URLs
need to be separated with a ''|'', and the set of URLs needs to be enclosed in double quotes. Do //not//
enclose each URL in double quotes separately! Correct example:
''homepageurl="https://www.google.de|https://wiki.x2go.org"''
+ * ''initrdblankdpmsfix'' is the same as ''earlyblankdpmsfix'', only that it
activates in the initial ramdisk already. Like ''earlyblankdpmsfix'', it can
also be called as ''initrdblankdpmsfix=nnnn''. This parameter is useful if you
are affected by the //black screen at boot// issue, and you are not combining
squashfs and initrd into one file when netbooting. (feature available via
github repo, soon via x2go repo
too)
* ''ldap=ldap.example.com:389:cn=cngoeshere,dc=example,dc=com'' - this
allows you to specify an LDAP server to connect to - note that this is not
needed for LDAP-based authentication, only when you intend to store entire
session profiles in LDAP. You should really consider using the X2Go Session
Broker instead.
* ''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.
@@ -899,12 +900,18 @@
* ''tcedebug'' - this switches X2GoClient into debug mode and will also lead
to increased logging
to /var/log/x2goclient and to tty9
* ''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''.
* ''throttle=n|n:n:n:n:n'' - Will throttle down- and upload speed (''throttle=n'') or set throttling limits as follows: download:upload:smoothingtime:smoothinglength:latency. Defaults for up- and download are 10 (KiloBytes/s), 3.0 (seconds, using decimals is permitted) smoothingtime, 20 (KiloBytes), 0 (ms). for a detailed description of these parameters, see "man trickle". You can use the first 1, 2, 3, 4 or all 5 parameters. To set down- and/or upload speed to unlimited, use the letter "u" instead of a numeric value.
+ * ''x3270servers="host[:port][|host[:port]...]"'' - this is only available
in MiniDesktop mode. It allows you to specify one or more hosts (with optional ports) for
x3270 terminal emulation sessions that will be created as desktop shortcuts on the
thinclient. For a default 3270 connection, the port is 23 (telnet) and does not need to
be specified. For an SSL-encrypted
connection (recommended), the port is 992. Hosts may be IP addresses or DNS
names, and need to be separated with a ''|''. (feature available via github
repo, soon via x2go repo too)
+ ''x5250servers="host[:port][|host[:port]...]"'' - this is only available in
MiniDesktop mode. It allows you to specify one or more hosts (with optional ports) for
x5250 terminal emulation sessions that will be created as desktop shortcuts on the
thinclient. For a default 5250 connection, the port is 23 (telnet) and does not need to
be specified. For an SSL-encrypted connection (recommended), the port is 992. Hosts may
be IP addresses or DNS names, and need to be separated with a ''|''. Note that x5250
support is currently not part of the standard image available via git, as there is no
x5250 executable in Debian. You can try using x3270 instead, most modern IBM i (System i,
iSeries, AS/400) systems support 3270-type connections as well. If you need native 5250
support, say, with a commercial,
closed-source 5250 terminal emulator, please leave a message on the X2Go-User
Mailing List and we'll tell you if and how you can integrate that into your
build. (feature available via github repo, soon via x2go repo too)
* ''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
*
''xorgconfurl=tftp|http|https|ftp://your-http-server-ip-or-dns-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.
**Attention: Whoever manages to spoof the server name can inject rogue xorg
config files into your ThinClients.** To mitigate this risk, use HTTPS, where
the attacker would have to spoof both server name and matching certificate.
-
+ * ''xroot=[0xaabbcc|URI1[|URI2|...]]'' - can be used to set a local desktop background image or color (in hex format, with leading 0x, not leading #). On the main screen, this is only visible during startup, while additional screens will display whatever is set for them
when there is no active session. The background also becomes visible for a
short moment when the optional local screensaver activates or deactivates.
Specifying more than one image will cause the first image to show up on the
first screen, the second image on the second screen, and so on (feature
available via github repo, soon via x2go repo too).
+ * ''xrootmode=center|fill|scale|tile'' can be used to determine how the
local desktop background image(s) should be positioned. If the parameter has
been set, but something is wrong, it will default to a //grey mesh//
background. (feature available via github repo, soon via x2go repo too).
(feature available via github repo, soon via x2go repo too)
+ * ''xsaveridletime=n'' - this value determines how long the screen should
have been idle before the local slideshow screensaver sets in (value given in
seconds). We recommend using 60 seconds less than for the server-sided, locking
screensaver. (feature available via github repo, soon via
x2go repo too)
+ * ''xsaverimages=[URI1[|URI2|...]]'' - if you want a local, non-locking
slideshow screensaver, you can specify image URLs here. These Images will be
downloaded once, at boot. That way, one can display a slideshow without having
to push the images across the network every time. Especially for slow links,
this is the recommended way of running a slideshow screensaver. For security,
combine this with a locking screensaver on the server with only one slide or a
black background. (feature available via github repo, soon via x2go repo too)
+ * ''xsaverimgtime=n'' - this determines how long each slide of the local,
non-locking screensaver will be shown. (feature available via github repo, soon
via x2go repo too)
=== These are only intended to be used with TCE images stored on local media
===
* ''bwlimit=nnn'' - Will allow you to specify a bandwidth limit (valid
values: 1-100) in percent for the backgrounded update task.
* ''ntfs-uuid='' - Will be required for
updating images stored on NTFS filesystems. Full UUID as shown under /dev/disk/by-uuid/
is preferred, but can work with the volume serial number shown in the output of "vol
c:" as well.
* ''updatesleep=nnnnn'' - Will allow you to specify the upper limit (in
seconds) of the update timer's randomizer. Allowed range for upper limit:
240-32767. Will default to 900 if unset or set to an out-of-range value. Lower
limit is fixed at 120 seconds.
--
This mail was generated by DokuWiki at
https://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-commits