1.\" Copyright (c) 1985, 1991, 1993 2.\" The Regents of the University of California. 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.\" from: @(#)ttys.5 8.1 (Berkeley) 6/4/93 33.\" $Id: ttys.5,v 1.1.1.2 1996/04/13 15:33:16 joerg Exp $ 34.\" " 35.Dd June 4, 1993 36.Dt TTYS 5 37.Os 38.Sh NAME 39.Nm ttys 40.Nd terminal initialization information 41.Sh DESCRIPTION 42The file 43.Nm ttys 44contains information that is used by various routines to initialize 45and control the use of terminal special files. 46This information is read with the 47.Xr getttyent 3 48library routines. 49There is one line in the 50.Nm ttys 51file per special device file. 52Fields are separated by tabs and/or spaces. 53Fields comprised of more than one word should be enclosed in double 54quotes (``"''). 55Blank lines and comments may appear anywhere in the file; comments 56are delimited by hash marks (``#'') and new lines. 57Any unspecified fields will default to null. 58.Pp 59The first field is the 60name of the terminal special file as it is found in 61.Pa /dev . 62.Pp 63The second field of the file is the command to execute for the line, 64usually 65.Xr getty 8 , 66which initializes and opens the line, setting the speed, waiting for 67a user name and executing the 68.Xr login 1 69program. 70It can be, however, any desired command, for example 71the start up for a window system terminal emulator or some other 72daemon process, and can contain multiple words if quoted. 73.Pp 74The third field is the type of terminal usually connected to that 75tty line, normally the one found in the 76.Xr termcap 5 77data base file. 78The environment variable 79.Dv TERM 80is initialized with the value by 81either 82.Xr getty 8 83or 84.Xr login 1 . 85.Pp 86The remaining fields set flags in the 87.Fa ty_status 88entry (see 89.Xr getttyent 3 ) 90or specify a window system process that 91.Xr init 8 92will maintain for the terminal line. 93.Pp 94As flag values, the strings ``on'' and ``off'' specify that 95.Xr init 96should (should not) execute the command given in the second field, 97while ``secure'' (if ``on'' is also specified) allows users with a 98uid of 0 to login on 99this line. 100The flags ``local'', ``rtscts'', ``mdmbuf'', and ``softcar'' 101modify the default behaviour of the terminal line, and their actions 102are driver dependent. 103The ``local'' flag causes the driver to 104treat the line as if it locally connected. 105The ``rtscts'' flag 106instructs the driver to use RTS/CTS hardware flow control, if 107possible. 108The ``mdmbuf'' flag instructs the driver to use 109DTR/DCD flow control, if possible. 110The ``softcar'' flag causes the driver to ignore 111hardware carrier on the line. 112These flag fields should not be quoted. 113.Pp 114The string ``window='' may be followed by a quoted command 115string which 116.Xr init 117will execute 118.Em before 119starting the command specified by the second field. 120.Sh EXAMPLES 121.Bd -literal 122# root login on console at 1200 baud 123console "/usr/libexec/getty std.1200" vt100 on secure 124# dialup at 1200 baud, no root logins 125ttyd0 "/usr/libexec/getty d1200" dialup on # 555-1234 126# Mike's terminal: hp2621 127ttyh0 "/usr/libexec/getty std.9600" hp2621-nl on # 457 Evans 128# John's terminal: vt100 129ttyh1 "/usr/libexec/getty std.9600" vt100 on # 459 Evans 130# terminal emulate/window system 131ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0" 132# Network pseudo ttys -- don't enable getty 133ttyp0 none network 134ttyp1 none network off 135.Ed 136.Sh FILES 137.Bl -tag -width /etc/ttys -compact 138.It Pa /etc/ttys 139.El 140.Sh SEE ALSO 141.Xr login 1 , 142.Xr getttyent 3 , 143.Xr ttyslot 3 , 144.Xr gettytab 5 , 145.Xr termcap 5 , 146.Xr getty 8 , 147.Xr init 8 148.\".Xr init 8 , 149.\".Xr ttyflags 8 150.Sh HISTORY 151A 152.Nm 153file appeared in 154.At v6 . 155