1.\" Copyright (c) 1985, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.roff% 5.\" 6.\" @(#)ttys.5 8.1 (Berkeley) 06/04/93 7.\" 8.Dd 9.Dt TTYS 5 10.Os 11.Sh NAME 12.Nm ttys 13.Nd terminal initialization information 14.Sh DESCRIPTION 15The file 16.Nm ttys 17contains information that is used by various routines to initialize 18and control the use of terminal special files. 19This information is read with the 20.Xr getttyent 3 21library routines. 22There is one line in the 23.Nm ttys 24file per special device file. 25Fields are separated by tabs and/or spaces. 26Fields comprised of more than one word should be enclosed in double 27quotes (``"''). 28Blank lines and comments may appear anywhere in the file; comments 29are delimited by hash marks (``#'') and new lines. 30Any unspecified fields will default to null. 31.Pp 32The first field is the 33name of the terminal special file as it is found in 34.Pa /dev . 35.Pp 36The second field of the file is the command to execute for the line, 37usually 38.Xr getty 8 , 39which initializes and opens the line, setting the speed, waiting for 40a user name and executing the 41.Xr login 1 42program. 43It can be, however, any desired command, for example 44the start up for a window system terminal emulator or some other 45daemon process, and can contain multiple words if quoted. 46.Pp 47The third field is the type of terminal usually connected to that 48tty line, normally the one found in the 49.Xr termcap 5 50data base file. 51The environment variable 52.Dv TERM 53is initialized with the value by 54either 55.Xr getty 8 56or 57.Xr login 1 . 58.Pp 59The remaining fields set flags in the 60.Fa ty_status 61entry (see 62.Xr getttyent 3 ) 63or specify a window system process that 64.Xr init 8 65will maintain for the terminal line. 66.Pp 67As flag values, the strings ``on'' and ``off'' specify that 68.Xr init 69should (should not) execute the command given in the second field, 70while ``secure'' (if ``on'' is also specified) allows users with a 71uid of 0 to login on 72this line. 73These flag fields should not be quoted. 74.Pp 75The string ``window='' may be followed by a quoted command 76string which 77.Xr init 78will execute 79.Em before 80starting the command specified by the second field. 81.Sh EXAMPLES 82.Bd -literal 83# root login on console at 1200 baud 84console "/usr/libexec/getty std.1200" vt100 on secure 85# dialup at 1200 baud, no root logins 86ttyd0 "/usr/libexec/getty d1200" dialup on # 555-1234 87# Mike's terminal: hp2621 88ttyh0 "/usr/libexec/getty std.9600" hp2621-nl on # 457 Evans 89# John's terminal: vt100 90ttyh1 "/usr/libexec/getty std.9600" vt100 on # 459 Evans 91# terminal emulate/window system 92ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0" 93# Network pseudo ttys -- don't enable getty 94ttyp0 none network 95ttyp1 none network off 96.Ed 97.Sh FILES 98.Bl -tag -width /etc/ttys -compact 99.It Pa /etc/ttys 100.El 101.Sh SEE ALSO 102.Xr login 1 , 103.Xr getttyent 3 , 104.Xr ttyslot 3 , 105.Xr gettytab 5 , 106.Xr termcap 5 , 107.Xr getty 8 , 108.Xr init 8 109.Sh HISTORY 110A 111.Nm 112file appeared in 113.At v6 . 114