diff options
| author | Matthieu Herrb <matthieu@cvs.openbsd.org> | 2017-02-28 07:04:29 +0000 |
|---|---|---|
| committer | Matthieu Herrb <matthieu@herrb.eu> | 2020-07-14 15:52:37 +0200 |
| commit | ecdedbcedac31ef3ac260d9d5072f01c242e9cbc (patch) | |
| tree | 87a0ffcde200d4478de693b3744afea787806e45 | |
| parent | 56555b26522e454ad613fe9d8152317b4e502752 (diff) | |
Remove some remaining XDMCP and remote X servers references.
| -rw-r--r-- | man/xenodm.man | 17 |
1 files changed, 5 insertions, 12 deletions
diff --git a/man/xenodm.man b/man/xenodm.man index 7c9ff80..90bd4df 100644 --- a/man/xenodm.man +++ b/man/xenodm.man @@ -52,12 +52,8 @@ xenodm \- X Display Manager .SH DESCRIPTION .I Xenodm manages a collection of X displays on the local host. -The design of -.I xenodm -was guided by the needs of X terminals as well as The Open Group standard -XDMCP, the \fIX Display Manager Control Protocol\fP. .I Xenodm -provides services similar to those provided by \fIinit\fP, \fIgetty\fP +provides services similar to those provided by \fIgetty\fP and \fIlogin\fP on character terminals: prompting for login name and password, authenticating the user, and running a ``session.'' .PP @@ -394,9 +390,7 @@ kills and restarts the server (if possible) and the session. generates and uses authorization for the local server connections. If authorization is used, \fBauthName\fP is a list of authorization mechanisms to use, separated by white space. -XDMCP connections dynamically specify which -authorization mechanisms are supported, so -\fBauthName\fP is ignored in this case. When \fBauthorize\fP is set for a +When \fBauthorize\fP is set for a display and authorization is not available, the user is informed by having a different message displayed in the login widget. By default, \fBauthorize\fP is ``true,'' \fBauthName\fP is ``MIT-MAGIC-COOKIE-1,'' or, if @@ -477,13 +471,12 @@ or, if the values starts with a slash (/), the name of a file containing server specifications, one per line. .PP Each specification -indicates a display which should constantly be managed and which is -not using XDMCP. -This method is used typically for local servers only. If the resource +indicates a display which should constantly be managed. +If the resource or the file named by the resource is empty, \fIxenodm\fP will exit. .PP Each specification consists of at least three parts: a display -name, a display class, a display type, and (for local servers) a command +name, a display class, a display type, and a command line to start the server. A typical entry for local display number 0 would be: .nf |