|
|
1.1 root 1: .\" @(#)ttys.5 6.4 (Berkeley) 5/20/86
2: .\"
3: .TH TTYS 5 "May 20, 1986"
4: .AT 3
5: .SH NAME
6: ttys \- terminal initialization data
7: .SH DESCRIPTION
8: The
9: .I ttys
10: file contains information that is used by various routines to initialize
11: and control the use of terminal special files. This information is read
12: with the
13: .IR getttyent (3)
14: library routines.
15: There is one line in the
16: .I ttys
17: file per special file.
18: Fields are separated by tabs and/or spaces.
19: Some fields may contain more than one word and should be enclosed
20: in double quotes.
21: Blank lines and comments can appear anywhere in the file; comments
22: are delimited by `#' and new line. Unspecified fields default to null.
23: The first field is the terminal's entry in the device directory, /dev.
24: The second field of the file is the command to execute for the line,
25: typically
26: .IR getty (8),
27: which performs such tasks as baud-rate recognition, reading the login name,
28: and calling
29: .IR login (1).
30: It can be, however, any desired command, for example
31: the start up for a window system terminal emulator or some other
32: daemon process, and can contain multiple words if quoted.
33: The third field is the type of terminal normally connected to that
34: tty line, as found in the
35: .IR termcap (5)
36: data base file.
37: The remaining fields set flags in the
38: .I ty_status
39: entry (see
40: .IR getttyent (3))
41: or specify a window system process that
42: .IR init (8)
43: will maintain for the terminal line.
44: As flag values,
45: the strings `on' and `off' specify whether
46: .I init
47: should execute the command
48: given in the second field,
49: while `secure' in addition to `on' allows root to login on
50: this line. These flag fields should not be quoted.
51: The string `window=' is followed by a quoted command
52: string which
53: .I init
54: will execute before starting
55: .IR getty .
56: If the line ends in a comment, the comment is included in the
57: .I ty_comment
58: field of the ttyent structure.
59: .PP
60: Some examples:
61: .PP
62: .nf
63: .ta \w'console\ 'u +\w'"/etc/getty std.9600"\ \ \ 'u +\w'hp2621-nl\ \ \ \ 'u +.7i
64: console "/etc/getty std.1200" vt100 on secure
65: ttyd0 "/etc/getty d1200" dialup on # 555-1234
66: ttyh0 "/etc/getty std.9600" hp2621-nl on # 254MC
67: ttyh1 "/etc/getty std.9600" plugboard on # John's office
68: ttyp0 none network
69: ttyp1 none network off
70: ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0"
71: .fi
72: .PP
73: The first example permits root login on the console at 1200 baud,
74: the second allows dialup at 1200 baud without root login,
75: the third and fourth allow login at 9600 baud with terminal types of
76: "hp2621-nl" and "plugboard" respectively,
77: the fifth and sixth line are examples of network pseudo ttys, which
78: should not have
79: .I getty
80: enabled on them,
81: and the last example shows a terminal emulator and window system
82: startup entry.
83: .SH FILES
84: /etc/ttys
85: .SH "SEE ALSO"
86: login(1), getttyent(3), gettytab(5), init(8), getty(8)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.