Each entry in the
StaticServers list indicates a
display which should constantly be
managed and which is not using XDMCP. This method is typically used only for
local X-Servers that are started by kdm, but kdm can manage externally
started (“foreign”) X-Servers as well, may they run on the
local machine or rather remotely.
The formal syntax of a specification is
for all X-Servers. “Foreign” displays differ in having
a host name in the display name, may it be
display name must be something that can
be passed in the
-display option to an X program. This string
is used to generate the display-specific section names, so be careful to match
The display name of XDMCP displays is derived from the display's address by
reverse host name resolution. For configuration purposes, the
localhost prefix from locally running XDMCP displays is
not stripped to make them distinguishable from local
X-Servers started by kdm.
display class portion is also used in the
display-specific sections. This is useful if you have a large collection of
similar displays (such as a corral of X terminals) and would like to set
options for groups of them.
When using XDMCP, the display is required to specify the display class,
so the manual for your particular X terminal should document the display
class string for your device. If it does not, you can run kdm in debug
mode and grep the log for “class”.
The displays specified in
ReserveServers will not be
started when kdm starts up, but when it is explicitly requested via
the command socket.
If reserve displays are specified, the KDE menu will have a
Start New Session item near the bottom; use that to
activate a reserve display with a new login session. The monitor will switch
to the new display, and you will have a minute to login. If there are no more
reserve displays available, the menu item will be disabled.
When kdm starts a session, it sets up authorization data for the
X-Server. For local servers, kdm passes
on the X-Server's command line to point it at its authorization data.
For XDMCP displays, kdm passes the authorization data to the X-Server
via the “Accept” XDMCP message.