summaryrefslogtreecommitdiff
path: root/system/xrdp
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 13:06:09 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:15 -0400
commit11ae2d19b571ce094d57f8b329b1ee81fe4eb507 (patch)
tree86e5f4c32658ba1c986bcd23e7f6991bc812f38d /system/xrdp
parentd9bc85f596180907999e80501b38abf9de7d4333 (diff)
downloadslackbuilds-11ae2d19b571ce094d57f8b329b1ee81fe4eb507.tar.gz
system/xrdp: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/xrdp')
-rw-r--r--system/xrdp/README66
1 files changed, 34 insertions, 32 deletions
diff --git a/system/xrdp/README b/system/xrdp/README
index e127d9d09a..f04525fa85 100644
--- a/system/xrdp/README
+++ b/system/xrdp/README
@@ -1,34 +1,36 @@
-Xrdp provides a fully functional Linux terminal server, capable of accepting
-connections from rdesktop and Microsoft's own terminal server/remote desktop
-clients. Xrdp uses Xvnc or xorgxrdp (which are installed separately) to manage
-the X session. This means a RDP client can connect to a VNC server on the
-xrdp server machine in addition to the RDP server. Xrdp can also act as a
-bridging server, allowing RDP clients to connect to other RDP or VNC servers
-through the xrdp server.
+Xrdp provides a fully functional Linux terminal server, capable of
+accepting connections from rdesktop and Microsoft's own terminal
+server/remote desktop clients. Xrdp uses Xvnc or xorgxrdp (which
+are installed separately) to manage the X session. This means a
+RDP client can connect to a VNC server on the xrdp server machine in
+addition to the RDP server. Xrdp can also act as a bridging server,
+allowing RDP clients to connect to other RDP or VNC servers through
+the xrdp server.
Xvnc is included with tigervnc (in Slackware /extra).
xorgxrdp can be compiled and installed after installing xrdp.
-By default, this script will make xrdp without PAM support since PAM is not
-installed in Slackware by default. The script supports building with PAM,
-but it is completely untested by us. If you want to enable PAM, run the
-script as follows:
+By default, this script will make xrdp without PAM support since
+PAM is not installed in Slackware by default. The script supports
+building with PAM, but it is completely untested by us. If you want
+to enable PAM, run the script as follows:
USE_PAM=YES ./xrdp.SlackBuild
-By default, this script will make xrdp without GVFS support, as it can cause
-a problem if a session is unexpectedly terminated leaving an orphan GVFS
-mount. (This can be corrected by logging into the server hosting xrdp and
-running 'fusermount -uz ~/thinclient_drives').
-If you want to use drive redirection and shared clipboard support,
-run the script as follows:
+By default, this script will make xrdp without GVFS support, as it
+can cause a problem if a session is unexpectedly terminated leaving
+an orphan GVFS mount. (This can be corrected by logging into the
+server hosting xrdp and running 'fusermount -uz ~/thinclient_drives').
+If you want to use drive redirection and shared clipboard support, run
+the script as follows:
USE_GVFS=YES ./xrdp.SlackBuild
-After installing xrdp there are some configuration files in /etc/xrdp that
-can be modified:
+After installing xrdp there are some configuration files in /etc/xrdp
+that can be modified:
** sesman.ini **
-sesman.ini has some useful options to take note of such as the ability to
-allow xrdp use by only a certain group and to specify the log location.
+sesman.ini has some useful options to take note of such as the ability
+to allow xrdp use by only a certain group and to specify the log
+location.
*NOTE:* The default log location is now /var/log/xrdp-sesman.log, and
the logs are rotated according to /etc/logrotate.d/xrdp-sesman added
by the script.
@@ -48,17 +50,17 @@ the logs are rotated according to /etc/logrotate.d/xrdp added
by the script.
** xrdp-xinitrc **
-xrdp-xinitrc by default tries to load one of several DE/WMs in order to
-start a X11rdp session. Change this as desired to load a specific DE/WM.
-A similar script can be executed on a per-user basis by creating an
-executable script at ~/.xrdp-xinitrc. A utility program, xrdp-xwmconfig,
-is included to allow you to use your xinit scripts during sessions.
-It works just like xwmconfig, so run it as root to set the global default,
-or run it as a normal user to set only the default for that user. See the
-sesman.ini man page for details about defining different names or locations
-for the startup scripts.
+xrdp-xinitrc by default tries to load one of several DE/WMs in order
+to start a X11rdp session. Change this as desired to load a specific
+DE/WM. A similar script can be executed on a per-user basis by
+creating an executable script at ~/.xrdp-xinitrc. A utility program,
+xrdp-xwmconfig, is included to allow you to use your xinit scripts
+during sessions. It works just like xwmconfig, so run it as root to
+set the global default, or run it as a normal user to set only the
+default for that user. See the sesman.ini man page for details about
+defining different names or locations for the startup scripts.
-If using xorgxrdp, you will likely need a /etc/X11/Xwrapper.config wrapper
-script containing a line:
+If using xorgxrdp, you will likely need a /etc/X11/Xwrapper.config
+wrapper script containing a line:
allowed_users = anybody
(See 'man Xwrapper.config' for details)