Changeset 555f708 for xsoft/other/tigervnc.xml
- Timestamp:
- 09/14/2020 09:57:04 PM (4 years ago)
- 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
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
xsoft/other/tigervnc.xml
r794a5d8 r555f708 91 91 </para> 92 92 </note> 93 94 <itemizedlist spacing="compact"> 95 <listitem> 96 <para> 97 Optional files: 98 <itemizedlist spacing="compact"> 99 <listitem> 100 <para><ulink url="&sources-anduin-http;/tigervnc/vncserver"/></para> 101 </listitem> 102 <listitem> 103 <para><ulink url="&sources-anduin-http;/tigervnc/vncserver.1"/></para> 104 </listitem> 105 </itemizedlist> 106 </para> 107 </listitem> 108 </itemizedlist> 93 109 94 110 <bridgehead renderas="sect3">Tigervnc Dependencies</bridgehead> … … 221 237 222 238 <para> 223 The user specific configuration files of vncserver resides 224 in the <filename class='directory'>.vnc</filename> directory in the user's 225 home directory. The <filename>xstartup</filename> file in that 226 directory is a script specifying what commands to be run 227 when a VNC desktop is started. If no <filename>xstartup</filename> file 228 exists, <command>vncserver</command> will try to start an xterm in a twm 229 session. An example <filename>xstartup</filename> would be: 239 The default installation of this package makes some changes in the way it 240 is used. The vncserver perl script is placed in /usr/libexec and the 241 server is designed to be run via a systemd style .service file or the 242 vncsession script as the root user. The man page for vncserver is placed 243 in section 8 of the man pages. The new procedures require a display 244 manager to be installed. 245 </para> 246 247 <para> 248 To restore the previous behavior, download the optional files listed 249 above and place the perl script into the /usr/bin directory. Ensure it 250 is executable (chmod a+x) by a non-privileged user. Put the downloaded 251 man page in /usr/share/man/man1. These files are from the 252 tigervnc-1.10.1 version of the package. 253 </para> 254 255 <para> 256 Using the previous procedures, the user specific configuration files of 257 vncserver reside in the <filename class='directory'>.vnc</filename> 258 directory in the user's home directory. The 259 <filename>xstartup</filename> file in that directory is a script 260 specifying what commands to run when a VNC desktop is started. If no 261 <filename>xstartup</filename> file exists, <command>vncserver</command> 262 will try to start an xterm in a twm session. An example 263 <filename>xstartup</filename> would be: 230 264 </para> 231 265 … … 237 271 <para> 238 272 The <filename>xstartup</filename> file must be executable for the 239 commands in it to be executed, so run 240 <command>chmod a+x ~/.vnc/xstartup</command>. 241 </para> 242 273 commands in it to be executed, so run <command>chmod a+x 274 ~/.vnc/xstartup</command>. 275 </para> 276 277 <para> 278 Set up the vnc passwd with <command>vncpasswd</command>. Then 279 server can then be started with the <command>vncserver</command> 280 command.. 281 See the man pages in section 1 for the vncserver for the server 282 system and vncviewer for the remote system. 283 </para> 243 284 244 285 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.