Added -fontpath description and FONT PATHS section to man page

1 files changed, 72 insertions, 1 deletions

diff --git a/xc/programs/Xserver/hw/dmx/Xdmx.man b/xc/programs/Xserver/hw/dmx/Xdmx.man
index 4a3e526c7..816610e42 100644
--- a/xc/programs/Xserver/hw/dmx/Xdmx.man
+++ b/xc/programs/Xserver/hw/dmx/Xdmx.man
@@ -108,6 +108,16 @@ overlapped backend displays.  This option is available for testing and
 benchmarking purposes.
 .sp
 .TP 8
+.BI "-fontpath"
+This option sets the
+.I Xdmx
+server's default font path.  This option can be specified mutiple times
+to accommodate multiple font paths.  See the
+.B "FONT PATHS"
+section below for very important information regarding setting the
+default font path.
+.sp
+.TP 8
 .BI "-configfile " filename
 Specify the configuration file that should be read.  Note that if the
 .B \-display
@@ -248,6 +258,67 @@ virtual example4 {
 }
 .fi
 .RE
+.SH "FONT PATHS"
+The font path used by the
+.I Xdmx
+front-end server will be propogated to each back-end server,which
+requires that each back-end server have access to the exact same font
+paths as the front-end server.  This can be most easily handled by
+either using a font server (e.g., xfs) or by remotely mounting the font
+paths on each back-end server, and then setting the
+.I Xdmx
+server's default font path with the
+-I "-fontpath"
+command line option described above.
+.PP
+For example, if you specify a font path with the following command line:
+.RS 8
+Xdmx :1 -display d0:0 -fontpath /usr/fonts/75dpi/ -fontpath /usr/fonts/Type1/ +xinerama
+.RE
+Then, /usr/fonts/75dpi/ and /usr/fonts/Type1/ must be valid font paths
+on the
+.I Xdmx
+server and all back-end server, which is d0 in this example.
+.PP
+Font servers can also be specified with the
+.I "-fontpath"
+option.  For example, let's assume that a properly configured font
+server is running on host d0.  Then, the following command line
+.RS 8
+Xdmx :1 -display d0:0 -display d1:0 -fontpath tcp/d0:7100 +xinerama
+.RE
+will initialize the front-end
+.I Xdmx
+server and each of the back-end servers to use the font server on d0.
+.PP
+Some fonts might not be supported by either the front-end or the
+back-end servers.  For exmaple, let's assume the front-end
+.I Xdmx
+server includes support Type1 fonts, but one of the back-end servers
+does not.  Let's also assume that the default font path for
+.I Xdmx
+includes Type1 fonts in its font path.  Then, when
+.I Xdmx
+intializes the default font path to load the default font, the font path
+that includes Type1 fonts (along with the other default font paths that are used by the
+.I Xdmx
+server) is sent to the back-end server that cannot handle Type1 fonts.
+That back-end server then rejects the font path and sends an error back
+to the
+.I Xdmx
+server.
+.I Xdmx
+then prints an error message and exits because it failed to set the
+default font path and was unable load the default font.
+.PP
+To fix this error, the offending font path must be removed from the
+default font path by using a different
+.I "-fontpath"
+command line option.
+.PP
+The
+.I "-fontpath"
+option can also be added to the configuration file as described above.
 .SH "COMMAND-LINE EXAMPLES"
 The backend machines are d0 and d1, core input is from the pointer and
 keyboard attached to d0, clients will refer to :1 when opening windows:
@@ -297,7 +368,7 @@ Xdmx :1 -configfile filename -config example2
 .SH FILES
 ..
 .SH "SEE ALSO"
-X(__miscmansuffix__), Xserver(1), xdmxconfig(1), vdltodmx(1)
+X(__miscmansuffix__), Xserver(1), xdmxconfig(1), vdltodmx(1), xfs(1)
 .SH AUTHORS
 Kevin E. Martin
 .I <kem@redhat.com>,