BSD 4_3_Reno development

[unix-history] / usr / share / man / cat5 / ttys.0

TTYS(5)                       1990                        TTYS(5)



N\bNA\bAM\bME\bE
    ttys - terminal initialization data

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
    The _\bt_\bt_\by_\bs file contains information that is used by various
    routines to initialize and control the use of terminal spe-
    cial files.  This information is read with the _\bg_\be_\bt_\bt_\bt_\by_\be_\bn_\bt(3)
    library routines.  There is one line in the _\bt_\bt_\by_\bs 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 direc-
    tory, ``/dev''.

    The second field of the file is the command to execute for
    the line, typically _\bg_\be_\bt_\bt_\by(8), which performs such tasks as
    baud-rate recognition, reading the login name, and calling
    _\bl_\bo_\bg_\bi_\bn(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 _\bt_\be_\br_\bm_\bc_\ba_\bp(5) data
    base file.  The environmental variable ``TERM'' is initial-
    ized with the value by either _\bg_\be_\bt_\bt_\by(8) or _\bl_\bo_\bg_\bi_\bn(1).

    The remaining fields set flags in the _\bt_\by__\bs_\bt_\ba_\bt_\bu_\bs entry (see
    _\bg_\be_\bt_\bt_\bt_\by_\be_\bn_\bt(3)) or specify a window system process that
    _\bi_\bn_\bi_\bt(8) will maintain for the terminal line.

    As flag values, the strings ``on'' and ``off'' specify that
    _\bi_\bn_\bi_\bt 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 _\bi_\bn_\bi_\bt will execute b\bbe\bef\bfo\bor\bre\be starting the command
    specified by the second field.

E\bEX\bXA\bAM\bMP\bPL\bLE\bES\bS
    # root login on console at 1200 baud
    console   "/usr/libexec/getty std.1200" vt100     on secure
    # dialup at 1200 baud, no root logins
    ttyd0     "/usr/libexec/getty d1200"    dialup    on   # 555-1234
    # Mike's terminal: hp2621
    ttyh0     "/usr/libexec/getty std.9600" hp2621-nl on   # 457 Evans



Printed 7/27/90               June                              1






TTYS(5)                       1990                        TTYS(5)



    # John's terminal: vt100
    ttyh1     "/usr/libexec/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

F\bFI\bIL\bLE\bES\bS
    /etc/ttys

S\bSE\bEE\bE A\bAL\bLS\bSO\bO
    login(1), getttyent(3), ttyslot(3), gettytab(5), termcap(5),
    getty(8), init(8)









































Printed 7/27/90               June                              2