gettydefs(4)                                                   gettydefs(4)

NAME
     gettydefs - speed and terminal settings used by getty

DESCRIPTION
     The /etc/gettydefs file contains information used by getty(1M) to set
     up the speed and terminal settings for a line. It supplies information
     on what the login prompt should look like. It also supplies the speed
     to be tried next if the user indicates the current speed is not
     correct by pressing the BREAK key.

     Each entry in /etc/gettydefs has the following format:

          label# initial-flags # final-flags # login-prompt #next-label

     Each entry is followed by a blank line. Lines that begin with # are
     ignored and may be used to comment the file. The various fields can
     contain quoted characters of the form \b, \n, \c, etc. as well as
     \nnn, where nnn is the octal value of the desired character. The vari-
     ous fields are:

     label     This is the string against which getty(1M) tries to match
               its second argument. It is often the speed, such as 1200, at
               which the terminal is supposed to run, but it needn't be
               (see below).

     initial-flags
               These flags are the initial ioctl(2) settings to which the
               terminal is to be set if a terminal type is not specified to
               getty(1M). getty(1M) understands the symbolic names speci-
               fied in /usr/include/sys/termio.h [see termio(7)]. Normally
               only the speed flag is required in the initial-flags.
               getty(1M) automatically sets the terminal to raw input mode
               and takes care of most of the other flags. The initial-flag
               settings remain in effect until getty(1M) executes login(1).

     final-flags
               These flags take the same values as the initial-flags and
               are set just prior to getty(1M) executing login. The speed
               flag is again required. The composite flag SANE takes care
               of most of the other flags that need to be set so that the
               processor and terminal are communicating in a rational
               fashion. The other two commonly specified final-flags are
               TAB3, so that tabs are sent to the terminal as spaces, and
               HUPCL, so that the line is hung up on the final close.

     login-prompt
               This entire field is printed as the login-prompt. Unlike the
               above fields where white space is ignored (a space, tab or
               new-line), they are included in the login-prompt field.

     next-label
               This indicates the next label of the entry in the table that



Page 1                       Reliant UNIX 5.44                Printed 11/98

gettydefs(4)                                                   gettydefs(4)

               getty(1M) should use if the user presses the BREAK key or
               the input cannot be read. Usually, a series of speeds are
               linked together in this fashion, into a closed set. For
               instance, 2400 linked to 1200, which in turn is linked to
               300, which finally is linked to 2400.

     If getty(1M) is called without a second argument, then the first entry
     of /etc/gettydefs is used, thus making the first entry of
     /etc/gettydefs the default entry. It is also used if getty(1M) can't
     find the specified label. If /etc/gettydefs itself is missing, there
     is one entry built into the command which will bring up a terminal at
     300 baud.

     It is strongly recommended that after making or modifying
     /etc/gettydefs, it be run through getty(1M) with the check option to
     be sure there are no errors.

FILES
     /etc/gettydefs

SEE ALSO
     login(1), getty(1M), ioctl(2), termio(7).
































Page 2                       Reliant UNIX 5.44                Printed 11/98