Graphics Administration Guide (October 2009)

Dynamically loaded modules are recorded by the X Server in the /var/X11/Xserver/logs
directory. The log file reflects the display identifier for a given run. Only the last invocation
against a given display identifier is retained. The log file contains the parsed contents of the
XF86Config file and the full path name for all dynamically loaded modules for the given X Server
invocation. Deferred loaded modules are recorded as they are referenced.
NOTE: Altering or removing files under /usr/lib/X11/Xserver may prevent the X Server
from running.
features
cursor scaling
There are times when the standard X11 cursors are difficult to see on the screen. The effect is
compounded on large displays. Two options are available in the X Server that instruct the X
Server to scale all X11 cursors (both user-defined and built-in cursors) by a user-defined value.
Cursor Scaling is indicated with the following syntax in the XF86Config file:
Section “ServerLayout”
. . .
Option “CursorScaleFactor” “n”
Option “MaxCursorSize” “Size”
. . .
EndSection
Where n = 1, 2, 3, …
Where Size = 2, 4, 8, 16, 32, 64, …
For example, n=2 instructs the X Server to scale all cursors by “2x” so that a 16x16 cursor becomes
a 32x32 cursor and a 9x9 cursor becomes an 18x18 cursor, etc.
If the scaled width or height of any cursor is greater than Size, the scale factor is reduced so that
the net size of the cursor fits into a Size x Size rectangle. Size needs to be a power of two.
The default value for “n” is 1, or no scaling. The default value for “Size” is 64, or 64 x 64 maximum
size.
virtual frame buffer (Xvfb)
Xvfb(1) is an X Server that does not require display hardware or input devices. It emulates a
video frame buffer by using the system’s virtual memory.
Xvfb may be used for: rendering with non-standard depths and screen configurations, software
rendering, providing a way to run applications that don't need an X Server but for some reason
insist on having one, etc.
Generally the user application must use functions such as XGetImage(3) in order to see what
was rendered.
security
See Xf86(1) for information on configuring the Xf86 security policies, files and settings.
connecting to the network
The X Server supports client connections via a platform-dependent subset of the following
transport types: TCP/IP and Unix Domain sockets.
granting access
Information on X Server authorization may be found in the Xf86(1) man pages.
24 configuring X Server on HP-UX (OEM graphics cards)