|
|
1.1 root 1: .TH X 8C "25 January 1986" "X Version 10"
2: .SH NAME
3: X - X window system server
4: .SH SYNOPSIS
5: .B X
6: <display> [ option ... ] <tty>
7: .SH DESCRIPTION
8: .I X
9: is the window system server.
10: It is normally run automatically by \fIinit(8)\fP,
11: which provides the tty argument.
12: The display argument is the number of the bitmap display to service.
13: The number is typically in the range 0-6, and defines the ports the
14: server will accept connections on and the filename of the device.
15: .PP
16: The program \fIxinit(8)\fP is usually used to start
17: X interactively.
18: .PP
19: Connections through the Unix domain, through TCP, and through DECnet are
20: currently possible. The connections actually accepted by a server depend
21: on how it was compiled. Unix domain connections are through \fI/dev/X*\fP,
22: where * is the display number.
23: TCP connections are through ports 5800+N (VAX byte order)
24: and 5900+N (68000 byte order), where N is the display number. DECnet
25: connections are through object name ``X*'', where * is the display number.
26: .SH
27: OPTIONS
28: .PP
29: See the \fIX(1)\fP manual page for a list of command line options.
30: .SH
31: INITIALIZATION
32: .PP
33: \fIX(1)\fP and your first \fIxterm(1)\fP are normally started by the
34: \fIinit(8)\fP program.
35: .sp
36: A typical line in \fI/etc/ttys\fP might be:
37: .sp
38: .nf
39: ttyv0 "/etc/xterm -L =-1+1 :0" xterm on secure window="/etc/Xvs100 0 -c -l"
40: .fi
41: .sp
42: However, if you want the xterm to run on a different machine, you might have:
43: .sp
44: .nf
45: remote "/etc/X 0 -l -c" xterm on secure
46: .fi
47: .sp
48: on the server machine and
49: .sp
50: .nf
51: ttyv0 "/exe/xterm -L =-1+1 orpheus:0" xterm on secure
52: .fi
53: .sp
54: on the client machine.
55: .sp
56: .I X
57: maintains an access control list for accepting connections. The host where
58: the server runs is initially on the list.
59: In addition, hosts listed the file
60: \fI/etc/X*.hosts\fP,
61: where \fI*\fP is the display number, are also initially on the list.
62: The format of this file is a list of host names, one per line. DECnet hosts
63: are distinguished from Internet hosts by the existance of a trailing ``::'' in
64: the name.
65: The access control list can be manipulated with \fIxhost(1)\fP.
66: .sp
67: .I X
68: will catch the SIGHUP signal sent by \fIinit(8)\fP
69: after the initial process (usually
70: the login \fIxterm(1)\fP) started on the display terminates.
71: This signal causes all connections to be closed (thereby ``disowning'' the
72: terminal), all resources to be freed, and all defaults restored.
73: .sp
74: The X protocol is documented in ``X.doc''.
75: Note that while X is running, all access to the display must be through
76: the window system.
77: .SH "SEE ALSO"
78: X(1), xinit(1), xterm(1), bitmap(1), xwm(1), xhost(1), xload(1), xset(1), qv(4), vs(4), init(8)
79: .SH DIAGNOSTICS
80: Are too numerous to list them all.
81: If run from \fIinit(8)\fP, errors are logged in the file \fI/usr/adm/X*msgs\fP,
82: where * is the display number. Otherwise, errors go to error output.
83: .sp
84: `fatal error: No such device or address at Opening' usually means
85: someone else (like an existing X) has the display open.
86: .sp
87: `fatal error: No such file or directory at Initializing' usually means
88: the VS100 firmware was not found or that the device file for the display
89: does not exist.
90: .SH FILES
91: .ta \w'/usr/new/lib/X/s-code 'u
92: /etc/X*.hosts Initial access control list
93: .br
94: /usr/new/lib/X/font VS100/QVSS font directory
95: .br
96: /usr/new/lib/X/s-code VS100 firmware directory
97: .br
98: /dev/vs* VS100 devices
99: .br
100: /dev/qd* QDSS devices
101: .br
102: /dev/mouse QVSS device
103: .br
104: /dev/X* Unix domain socket (if configured)
105: .br
106: /usr/adm/X*msgs Error log file
107: .SH BUGS
108: The option syntax is inconsistent with itself and \fIxset(1)\fP.
109: .sp
110: If
111: .I X
112: dies before its clients, new clients won't be able to connect until all
113: existing connections have their TCP TIME_WAIT timers expire.
114: .SH AUTHOR
115: Bob Scheifler (MIT-LCS).
116: .br
117: Copyright (c) 1984, 1985, 1986, by Massachusetts Institute of Technology.
118: .br
119: See \fIX(1)\fP for a complete copyright notice.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.