dmx/man/Xdmx.man

38 back-end X servers.  All of the visible rendering is passed to the
39 back-end X servers.  Clients connect to the
47 communicates to the back-end X servers using the standard X11 protocol,
57 This specifies the name(s) of the back-end X server display(s) to connect
59 one back-end display.  The first is used as screen 0, the second as screen 1,
62 environment variable is used as the single back-end X server display.
95 If the display-name is a back-end server, then core input events are
149 back-end server (the one used for screen 0).  The console window shows
150 the layout of the back-end display(s) and pointer movements and key
181 overlapped back-end displays.  This option is available for testing and
212 is in seconds.  The screens is a count of the number of back-end screens
259 Disable use of the XKB extension for communication with the back end
267 default visual from those available on the back-end X server, the first
293 glXSwapBuffers request, Xdmx relays that request to each back-end X
296 buffering can lead to the set of back-end X servers handling the swap
298 issued to each back-end X server after sending the swap buffers request.
300 swap buffers requests) and wait until the back-end X servers have
315 glFinish() request to each back-end X server after sending the swap
322 This option ignores font paths that are not available on all back-end
524 front-end server will be propagated to each back-end server,which
525 requires that each back-end server have access to the exact same font
528 paths on each back-end server, and then setting the
541 server and all back-end server, which is d0 in this example.
552 server and each of the back-end servers to use the font server on d0.
555 back-end servers.  For example, let's assume the front-end
557 server includes support Type1 fonts, but one of the back-end servers
566 server) is sent to the back-end server that cannot handle Type1 fonts.
567 That back-end server then rejects the font path and sends an error back
584 The back-end machines are d0 and d1, core input is from the pointer and
609 to another VC (possibly back to another X session running on the local