Changeset 019bc05

Timestamp:

10/22/2020 03:18:25 AM (4 years ago)

Author:

Douglas R. Reno <renodr@…>

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:

f433fbd

Parents:

279fc64

Message:

Submit systemd-specific configuration for TigerVNC

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

Files:

• introduction/welcome/changelog.xml (modified) (1 diff)
• xsoft/other/tigervnc.xml (modified) (5 diffs)

introduction/welcome/changelog.xml

@@ -45 +45 @@
       <para>October 21st, 2020</para>
       <itemizedlist>
+        <listitem revision="systemd">
+          <para>[renodr] - Add configuration instructions for the systemd 
+          variant of TigerVNC.</para>
+        </listitem>
         <listitem>
           <para>[renodr] - Adapt gnome-nettool to work with current versions of

xsoft/other/tigervnc.xml

@@ -95 +95 @@
       <listitem>
         <para>
+          Required patch:
+          <ulink url="&patch-root;/tigervnc-&tigervnc-version;-configuration_fixes-1.patch"/>
+        </para>
+      </listitem>
+      <listitem>
+        <para>
           Optional files:
             <itemizedlist spacing="compact">
@@ -102 +108 @@
               <listitem>
                 <para><ulink url="&sources-anduin-http;/tigervnc/vncserver.1"/></para>
+              </listitem>
+              <listitem>
+                <para><ulink url="&sources-anduin-http;/tigervnc/Xsession"/></para>
               </listitem>
             </itemizedlist>
@@ -135 +144 @@
   <sect2 role="installation">
     <title>Installation of Tigervnc</title>
+
+    <para>
+      First, make adjustments to the configuration files to make them
+      compatible with LFS systems:
+      <!-- Replaces an incompatible PAM file and disables SELinux support
+           in systemd units. Also modifies the search path for
+           /usr/libexec/vncserver to include /etc/X11/tigervnc -->
+    </para>
+
+<screen><userinput remap="pre">patch -Np1 -i ../tigervnc-&tigervnc-version;-configuration_fixes-1.patch</userinput></screen>
 
     <para>
@@ -188 +207 @@
 
 [ -e /usr/bin/Xvnc ] || ln -svf $XORG_PREFIX/bin/Xvnc /usr/bin/Xvnc</userinput></screen>
+
+   <para revision="sysv">
+     Finally, modify the PAM file to be compatible with elogind:
+   </para>
+
+<screen role="root" revision="sysv"><userinput>sed -i 's/pam_systemd.so/pam_elogind.so/' /etc/pam.d/tigervnc</userinput></screen>
+
 <!-- These are installed as part of 'make install' for the client.
     <para>
@@ -283 +309 @@
     </para>
 
+    <bridgehead renderas="sect3" revision="systemd">Server Configuration</bridgehead>
+
+    <note revision="systemd">
+      <para>
+        This section is optional and is only useful if you want to have VNC
+        sessions launch on system startup. Both configuration methods can 
+        coexist on the same system.
+      </para>
+    </note>
+
+    <para revision="systemd">
+      On systemd systems, another method of configuration is available.
+      This configuration provides the added benefit of having a systemd scope
+      get started for VNC sessions, which allows desktop environments like
+      <application>GNOME</application> to autostart services once the VNC
+      session is started. This configuration also gives the added benefit
+      of starting VNC Sessions on system startup. To setup the VNC server
+      in this fashion, follow these instructions.
+    </para>
+
+    <para revision="systemd">
+       First, install a rudimentary Xsession file so that the VNC server
+       can initialize X sessions properly:
+    </para>
+
+<screen role="root" revision="systemd"><userinput>install -vdm755 /etc/X11/tigervnc &amp;&amp;
+install -v -m755 ../Xsession /etc/X11/tigervnc</userinput></screen>
+
+    <para revision="systemd">
+      Next, setup a user mapping in 
+      <filename>/etc/tigervnc/vncserver.users</filename>. This tells the VNC
+      Server which session is allocated to a user.
+      <!-- For example: :1=renodr will assign 'renodr' to :1 -->
+    </para>
+
+<screen role="root" revision="systemd"><userinput>echo ":1=$(whoami)" >> /etc/tigervnc/vncserver.users</userinput></screen>
+
+    <para revision="systemd">
+      Next, setup a configuration file to tell
+      <application>vncserver</application> which desktop environment should be
+      used and what display geometry should be used. There are several other
+      options that can be defined in this file, but they are outside the scope
+      of BLFS.
+    </para>
+
+<screen revision="systemd"><userinput>cat &gt; ~/.vnc/config &lt;&lt; EOF
+<literal># Begin ~/.vnc/config
+
+session=LXDE      # The session must match one listed in /usr/share/xsessions.
+geometry=1024x768
+
+# End ~/.vnc/config</literal>
+EOF</userinput></screen>
+
+    <para revision="systemd">
+      To start the VNC Server, run the following command:
+    </para>
+
+<screen role="root" revision="systemd"><userinput>systemctl start vncserver@:1</userinput></screen>
+
+    <para revision="systemd">
+      To start the VNC Server when the system boots, run the following command:
+    </para>
+
+<screen role="root" revision="systemd"><userinput>systemctl enable vncserver@:1</userinput></screen>
+
   </sect2>