[unix-history] / usr / src / libexec / getty / ttys.5

.\"	@(#)ttys.5	6.1 (Berkeley) %G%
.\"
.TH TTYS 5  ""
.AT 3
.SH NAME
ttys \- terminal initialization data
.SH DESCRIPTION
The
.I ttys
file contains information that is used by various routines to initialize
and control the use of terminal special files. This information is read
with the
.IR getttyent (3)
library routines.
There is one line in the 
.I ttys
file per special file.
Fields are separated by tabs and/or spaces.
A field of more than one word may be enclosed by quotes.
Blank lines and comments can appear anywhere in the file; comments
are delimited by `#' and new line. Unspecified fields default to
the empty string or zero as appropriate.
The first field is the terminal's entry in the device directory, /dev.
The second field of the file is the command to execute for the line,
typically
.IR getty (8),
which performs such tasks as baud-rate recognition, reading the login name,
and calling
.IR login (1).
It can be, however, any command you wish, for example
the start up for a window system terminal emulator or maintain other
daemon processes.
The third field is the type of terminal normally connected to the
terminal special file as found in the
.IR termcap (5)
data base file.
The remaining fields are flags to be set in the
.I ty_status
entry (see
.IR getttyent (3))
or for a window system process indicated by
the "window" keyword that
.IR init(8)
will maintain for the terminal line.
If the line ends in a comment, the comment is included in the
.I ty_comment
field of the ttyent structure.
.PP
Some examples:
.PP
.nf
console "/etc/getty std.1200" vt100 on secure
ttyd0 "/etc/getty d1200" dialup on
ttyh0 "/etc/getty std.9600" hp2621-nl on
ttyh1 "/etc/getty std.9600" plugboard on
ttyp0 none network
ttyp1 none network off
ttyv0 "/etc/xpty -L :0" vs100 on window="/etc/X 0"
.fi
.PP
The first example permits root login on the console at 1200 baud,
the second allows dialup at 1200 baud without root login,
the third and fourth allow login at 9600 baud with terminal types of
"hp2621-nl" and "plugboard" respectively,
the fifth and sixth line are examples of network pseudo ttys, which
should not have getty enabled on them,
and the last example shows a terminal emulator and window system
startup entry.
.SH FILES
/etc/ttys
.SH "SEE ALSO"
getttyent(3), gettytab(5), init(8), getty(8), login(1)
Commit	Line	Data
3892b435	1	.\" @(#)ttys.5 6.1 (Berkeley) %G%
6d85239e	2	.\"
3892b435	3	.TH TTYS 5 ""
6d85239e KM	4	.AT 3
	5	.SH NAME
	6	ttys \- terminal initialization data
	7	.SH DESCRIPTION
	8	The
	9	.I ttys
3892b435 KM	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.
5dc2d425 KM	15	There is one line in the
	16	.I ttys
	17	file per special file.
3892b435 KM	18	Fields are separated by tabs and/or spaces.
	19	A field of more than one word may be enclosed by quotes.
	20	Blank lines and comments can appear anywhere in the file; comments
	21	are delimited by `#' and new line. Unspecified fields default to
	22	the empty string or zero as appropriate.
	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
6d85239e	26	.IR getty (8),
5dc2d425	27	which performs such tasks as baud-rate recognition, reading the login name,
6d85239e	28	and calling
3892b435 KM	29	.IR login (1).
	30	It can be, however, any command you wish, for example
	31	the start up for a window system terminal emulator or maintain other
	32	daemon processes.
	33	The third field is the type of terminal normally connected to the
	34	terminal special file as found in the
	35	.IR termcap (5)
	36	data base file.
	37	The remaining fields are flags to be set in the
	38	.I ty_status
	39	entry (see
	40	.IR getttyent (3))
	41	or for a window system process indicated by
	42	the "window" keyword that
	43	.IR init(8)
	44	will maintain for the terminal line.
	45	If the line ends in a comment, the comment is included in the
	46	.I ty_comment
	47	field of the ttyent structure.
	48	.PP
	49	Some examples:
	50	.PP
	51	.nf
	52	console "/etc/getty std.1200" vt100 on secure
	53	ttyd0 "/etc/getty d1200" dialup on
	54	ttyh0 "/etc/getty std.9600" hp2621-nl on
	55	ttyh1 "/etc/getty std.9600" plugboard on
	56	ttyp0 none network
	57	ttyp1 none network off
	58	ttyv0 "/etc/xpty -L :0" vs100 on window="/etc/X 0"
	59	.fi
	60	.PP
	61	The first example permits root login on the console at 1200 baud,
	62	the second allows dialup at 1200 baud without root login,
	63	the third and fourth allow login at 9600 baud with terminal types of
	64	"hp2621-nl" and "plugboard" respectively,
	65	the fifth and sixth line are examples of network pseudo ttys, which
	66	should not have getty enabled on them,
	67	and the last example shows a terminal emulator and window system
	68	startup entry.
6d85239e KM	69	.SH FILES
	70	/etc/ttys
	71	.SH "SEE ALSO"
3892b435	72	getttyent(3), gettytab(5), init(8), getty(8), login(1)