Changeset 555f708 for xsoft/other

Timestamp:

09/14/2020 09:57:04 PM (4 years ago)

Author:

Bruce Dubbs <bdubbs@…>

Branches:

10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

0b87037d

Parents:

794a5d8

Message:

Update tigervnc configuration description.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@23710 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• xsoft/other/tigervnc.xml (modified) (3 diffs)

xsoft/other/tigervnc.xml

@@ -91 +91 @@
       </para>
     </note>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>
+          Optional files:
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para><ulink url="&sources-anduin-http;/tigervnc/vncserver"/></para>
+              </listitem>
+              <listitem>
+                <para><ulink url="&sources-anduin-http;/tigervnc/vncserver.1"/></para>
+              </listitem>
+            </itemizedlist>
+        </para>
+      </listitem>
+    </itemizedlist>
 
     <bridgehead renderas="sect3">Tigervnc Dependencies</bridgehead>
@@ -221 +237 @@
 
     <para>
-      The user specific configuration files of vncserver resides
-      in the <filename class='directory'>.vnc</filename> directory in the user's
-      home directory.  The <filename>xstartup</filename> file in that
-      directory is a script specifying what commands to be run
-      when a VNC desktop is started.  If no  <filename>xstartup</filename> file
-      exists, <command>vncserver</command> will try to start an xterm in a twm
-      session.  An example <filename>xstartup</filename> would be:
+      The default installation of this package makes some changes in the way it
+      is used.  The vncserver perl script is placed in /usr/libexec and the
+      server is designed to be run via a systemd style .service file or the
+      vncsession script as the root user.  The man page for vncserver is placed 
+      in section 8 of the man pages.  The new procedures require a display 
+      manager to be installed.
+    </para>
+
+    <para>
+      To restore the previous behavior, download the optional files listed
+      above and place the perl script into the /usr/bin directory.  Ensure it
+      is executable (chmod a+x) by a non-privileged user. Put the downloaded
+      man page in /usr/share/man/man1.  These files are from the
+      tigervnc-1.10.1 version of the package.  
+    </para>
+    
+    <para>
+      Using the previous procedures, the user specific configuration files of
+      vncserver reside in the <filename class='directory'>.vnc</filename>
+      directory in the user's home directory.  The
+      <filename>xstartup</filename> file in that directory is a script
+      specifying what commands to run when a VNC desktop is started.  If no
+      <filename>xstartup</filename> file exists, <command>vncserver</command>
+      will try to start an xterm in a twm session.  An example
+      <filename>xstartup</filename> would be:
     </para>
 
@@ -237 +271 @@
     <para>
       The <filename>xstartup</filename> file must be executable for the
-      commands in it to be executed, so run
-      <command>chmod a+x ~/.vnc/xstartup</command>. 
-    </para>
-
+      commands in it to be executed, so run <command>chmod a+x
+      ~/.vnc/xstartup</command>.
+    </para>
+
+    <para>
+      Set up the vnc passwd with <command>vncpasswd</command>. Then 
+      server can then be started with the <command>vncserver</command>
+      command..  
+      See the man pages in section 1 for the vncserver for the server
+      system and vncviewer for the remote system.
+    </para>
 
   </sect2>