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