Copyright (c) 1985 The Regents of the University of California.
All rights reserved.

Redistribution and use in source and binary forms are permitted
provided that the above copyright notice and this paragraph are
duplicated in all such forms and that any documentation,
advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed
by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.

@(#)ttys.5 6.5 (Berkeley) 09/19/89

.AT 3 ttys - terminal initialization data The 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 getttyent (3) library routines. There is one line in the ttys file per special file. Fields are separated by tabs and/or spaces. Fields comprised of more than one word should be enclosed in double quotes (``"''). Blank lines and comments may appear anywhere in the file; comments are delimited by hash marks (``#'') and new lines. Any unspecified fields will default to null.

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 getty (8), which performs such tasks as baud-rate recognition, reading the login name, and calling login (1). It can be, however, any desired command, for example the start up for a window system terminal emulator or some other daemon process, and can contain multiple words if quoted.

The third field is the type of terminal usually connected to that tty line, normally the one found in the termcap (5) data base file. The environmental variable ``TERM'' is initialized with the value by either getty (8) or login (1).

The remaining fields set flags in the ty_status entry (see getttyent (3)) or specify a window system process that init (8) will maintain for the terminal line.

As flag values, the strings ``on'' and ``off'' specify that init should (should not) execute the command given in the second field, while ``secure'' (if ``on'' is also specified) allows users with a uid of 0 to login on this line. These flag fields should not be quoted.

The string ``window='' may be followed by a quoted command string which init will execute before starting the command specified by the second field.

# root login on console at 1200 baud
console "/sbin/getty std.1200" vt100 on secure
# dialup at 1200 baud, no root logins
ttyd0 "/sbin/getty d1200" dialup on # 555-1234
# Mike's terminal: hp2621
ttyh0 "/sbin/getty std.9600" hp2621-nl on # 457 Evans
# John's terminal: vt100
ttyh1 "/sbin/getty std.9600" vt100 on # 459 Evans
# terminal emulate/window system
ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0"
# Network pseudo ttys -- don't enable getty
ttyp0 none network
ttyp1 none network off

/etc/ttys login(1), getttyent(3), ttyslot(3), gettytab(5), termcap(5), getty(8), init(8)