This commit was generated by cvs2svn to track changes on a CVS vendor
[unix-history] / libexec / getty / ttys.5
CommitLineData
15637ed4
RG
1.\" Copyright (c) 1985, 1991 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\" notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\" notice, this list of conditions and the following disclaimer in the
11.\" documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\" must display the following acknowledgement:
14.\" This product includes software developed by the University of
15.\" California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\" may be used to endorse or promote products derived from this software
18.\" without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\" @(#)ttys.5 6.8 (Berkeley) 5/4/91
33.\"
34.Dd May 4, 1991
35.Dt TTYS 5
36.Os
37.Sh NAME
38.Nm ttys
39.Nd terminal initialization information
40.Sh DESCRIPTION
41The file
42.Nm ttys
43contains information that is used by various routines to initialize
44and control the use of terminal special files.
45This information is read with the
46.Xr getttyent 3
47library routines.
15637ed4
RG
48There is one line in the
49.Nm ttys
50file per special device file.
51Fields are separated by tabs and/or spaces.
52Fields comprised of more than one word should be enclosed in double
53quotes (``"'').
54Blank lines and comments may appear anywhere in the file; comments
55are delimited by hash marks (``#'') and new lines.
56Any unspecified fields will default to null.
57.Pp
58The first field is the
59name of the terminal special file as it is found in
60.Pa /dev .
61.Pp
62The second field of the file is the command to execute for the line,
63usually
64.Xr getty 8 ,
65which initializes and opens the line, setting the speed, waiting for
66a user name and executing the
67.Xr login 1
68program.
69It can be, however, any desired command, for example
70the start up for a window system terminal emulator or some other
71daemon process, and can contain multiple words if quoted.
72.Pp
73The third field is the type of terminal usually connected to that
74tty line, normally the one found in the
75.Xr termcap 5
76data base file.
77The environment variable
78.Dv TERM
79is initialized with the value by
80either
81.Xr getty 8
82or
83.Xr login 1 .
84.Pp
85The remaining fields set flags in the
86.Fa ty_status
87entry (see
88.Xr getttyent 3 )
89or specify a window system process that
90.Xr init 8
91will maintain for the terminal line.
92.Pp
93As flag values, the strings ``on'' and ``off'' specify that
94.Xr init
95should (should not) execute the command given in the second field,
96while ``secure'' (if ``on'' is also specified) allows users with a
97uid of 0 to login on
98this line.
99These flag fields should not be quoted.
100.Pp
101The string ``window='' may be followed by a quoted command
102string which
103.Xr init
104will execute
105.Em before
106starting the command specified by the second field.
107.Sh EXAMPLES
108.Bd -literal
109# root login on console at 1200 baud
110console "/usr/libexec/getty std.1200" vt100 on secure
111# dialup at 1200 baud, no root logins
112ttyd0 "/usr/libexec/getty d1200" dialup on # 555-1234
113# Mike's terminal: hp2621
114ttyh0 "/usr/libexec/getty std.9600" hp2621-nl on # 457 Evans
115# John's terminal: vt100
116ttyh1 "/usr/libexec/getty std.9600" vt100 on # 459 Evans
117# terminal emulate/window system
118ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0"
119# Network pseudo ttys -- don't enable getty
120ttyp0 none network
121ttyp1 none network off
122.Ed
123.Sh FILES
124.Bl -tag -width /etc/ttys -compact
125.It Pa /etc/ttys
126.El
127.Sh SEE ALSO
128.Xr login 1 ,
129.Xr getttyent 3 ,
130.Xr ttyslot 3 ,
131.Xr gettytab 5 ,
132.Xr termcap 5 ,
133.Xr getty 8 ,
134.Xr init 8
135.Sh HISTORY
136A
137.Nm
138file appeared in
139.At v6 .