X display manager
From Wikipedia, the free encyclopedia
In the X Window System, an X display manager runs as a program, allowing starting a session on an X server from the same or another computer.
A display manager presents the user with a login screen into which to insert username and password. A session starts when the user successfully enters a valid combination of username and password.
When the display manager runs on the user's computer, it starts the X server before presenting the user the login screen, optionally repeating when the user logs out. In this condition, the display manager realizes in the X Window System the functionality of init, getty and login on character-mode terminals. When the display manager runs on a remote computer, it acts like a telnet server, requesting username and password and starting a remote session.
X11 Release 3 introduced display managers in October 1988 with the aim of supporting the standalone X terminals then just coming onto the market. Various display managers continue in routine use to provide a graphical login prompt on standalone computer workstations running X. X11R4 introduced the X Display Manager Control Protocol (XDMCP) in december 1989 to fix problems in the X11R3 implementation.
Contents |
[edit] Local and remote display management
A display manager can run on the same computer where the user sits or on a remote one. In the first case, the display manager starts one or more X servers, displaying the login screen at the beginning and (optionally) every time the user logs out. In the second case, the display manager works according to the XDMCP protocol.
The XDMCP protocol mandates that the X server starts autonomously and connects to the display manager. In the X Window System paradigm, the server runs on the computer providing the display and input devices. A server can connect, using the XDMCP protocol, to a display manager running on another computer, requesting it to start the session. In this case, the X server acts as a graphical telnet client while the display manager acts like a telnet server: users start programs from the computer running the display manager, while their input and output take place on the computer where the server (and the user) sits.
An administrator can configure an X server running on the computer or terminal of the user either to connect to a specific display manager, or to display a list of suitable hosts running potential X display managers. An XDMCP Chooser program allows the user to select a host from among those the terminal can connect to:
- a predefined list of hosts and their respective network addresses;
- a list of hosts (on the local TCP/IP subnet) that the XDMCP server in turn obtains by a network broadcast
The XDMCP server will often present itself in this list. When the user selects a host from the list, the X server running on the local machine will connect to the selected remote computer's X display manager.
[edit] X Display Manager Control Protocol
The X Display Manager Control Protocol uses UDP port 177. An X server requests that a display manager start a session by sending a Query packet. If the display manager allows access for that X server, it responds by sending a Willing packet back to the X server. (The X server can also send BroadcastQuery or IndirectQuery packets to start a session.)
The display manager must authenticate itself to the server. To do this the X server sends a Request packet to the display manager, which returns an Accept packet. If the Accept packet contains the response the X server expects, the display manager is authenticated. Producing the correct response might require the display manager to have access to a secret key, for example. If the authentication succeeds, the X server sends a Manage packet to inform the display manager. Then, the display manager shows the login screen by connecting to the X server as a regular X client.
During the session, the server can send KeepAlive packets to the display manager at intervals. If the display manager fails to respond with an Alive packet within a certain time, the X server presumes that the display manager has ceased running, and can terminate the connection.
[edit] History
XDM (the X Window Display Manager) originated in X11R3. This version suffered from several problems, most notably when users switched X terminals off and on. In X11R3, XDM only knew about an X terminal from its entry in the Xservers file, but XDM only consulted this file when it started. Thus every time a user switched a terminal off and on, the system administrator had to send a SIGHUP signal to XDM to instruct it to rescan Xservers.
XDMCP arrived with the introduction of X11R4 (December 1989). With XDMCP, the X server must actively request a display manager connection from the host. An X server using XDMCP therefore no longer requires an entry in Xservers.
[edit] Available display managers
The X Window System supplies XDM as its standard display manager.
Programmers have developed other X display managers, both commercial and free, offering additional functionality over the basic display management:
- scologin (provided by SCO Open Desktop) also check for expired passwords and perform some administration tasks
- GDM (GNOME)
- KDM (provided by KDE) allows the user to graphically select, in the login screen, a window manager or desktop environment
- dtlogin (shipped with CDE)
- WINGs Display Manager (using the WINGs widget-set used in Window Maker)
- entrance (using the architecture used in Enlightenment v.17).
[edit] See also
[edit] References
- XDMCP documentation (compressed PostScript), from the X.Org CVS repository at freedesktop.org
- XDM manual page (XFree86.org)
- Linda Mui and Eric Pearce, X Window System Volume 8: X Window System Administrator's Guide for X11 Release 4 and Release 5, 3rd edition (O'Reilly and Associates, July 1993; softcover ISBN 0-937175-83-8)
