[system-administrators-guide/21] Xvnc file naming requirements

[stephenw]

commit aac9eb2a624b2ceb4db350f19c5054cb980679e9
Author: Stephen Wadeley <swadeley at redhat.com>
Date:   Thu Feb 5 19:23:03 2015 +0100

    Xvnc file naming requirements

 en-US/TigerVNC.xml |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
---
diff --git a/en-US/TigerVNC.xml b/en-US/TigerVNC.xml
index 1221bfb..447544b 100644
--- a/en-US/TigerVNC.xml
+++ b/en-US/TigerVNC.xml
@@ -47,6 +47,9 @@ A configuration file named <filename>/etc/systemd/system/vncserver at .service</fil
     <screen>
 <computeroutput>~]#&nbsp;</computeroutput><userinput>cp /lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service</userinput>
     </screen>
+    <para>
+    There is no need to include the display number in the file name because <systemitem>systemd</systemitem> automatically creates the appropriately named instance in memory on demand, replacing <literal>'%i'</literal> in the service file by the display number. For a single user it is not necessary to rename the file. For multiple users, a uniquely named service file for each user is required, for example, by adding the user name to the file name in some way. See <xref linkend="configuring-vncserver-2users" /> for details.
+    </para>
     </step>
     <step>
         <para>