A page in your DokuWiki was added or changed. Here are the details:
Date : 2019/01/17 18:24
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=1547749413
New Revision: https://wiki.x2go.org/doku.php/doc:howto:tce
Edit Summary: [What options are available under FURTHER-OPTIONS-GO-HERE?]
User : stefanbaur
@@ -901,9 +901,9 @@
* ''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)
+ * ''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).
--
This mail was generated by DokuWiki at
https://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-commits
