GETTYDEFS(4-SysV) RISC/os Reference Manual GETTYDEFS(4-SysV)
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 try next if
the user indicates the current speed is not correct by typ-
ing a <break> character.
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. 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 various fields are:
label This is the string against which getty
tries to match its second argument. It
is often the speed, such as 1200, at
which the terminal is supposed to run,
but it need not 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. The flags that getty under-
stands are the same as the ones listed
in /usr/include/sys/termio.h [see ter-
mio(7)]. (The exceptions are that any
flags of the form ``CNEWXXX'' or
``LNEWXXX'' are written as simply
``XXX'' in /etc/gettydefs. For example,
CNEWRTSCTS is written as RTSCTS in
/etc/gettydefs.) Normally only the speed
flag is required in the initial-flags.
getty automatically sets the terminal to
raw input mode and takes care of most of
the other flags. The initial-flag set-
tings remain in effect until getty exe-
cutes login(1).
final-flags These flags take the same values as the
initial-flags and are set just prior to
getty executes 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 proces-
sor and terminal are communicating in a
rational fashion. The other two
Printed 1/15/91 Page 1
GETTYDEFS(4-SysV) RISC/os Reference Manual GETTYDEFS(4-SysV)
commonly specified final-flags are TAB3,
so that tabs are sent to the terminal as
spaces, RTSCTS, so that hardware flow
control is used with a modem, 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 If this entry does not specify the
desired speed, indicated by the user
typing a <break> character, then getty
will search for the entry with next-
label as its label field and set up the
terminal for those settings. 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 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 can not 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 with the check
option to be sure there are no errors.
FILES
/etc/gettydefs
SEE ALSO
ioctl(2).
getty(1M), termio(7) in the System Administrator's Reference
Manual.
login(1) in the User's Reference Manual.
Page 2 Printed 1/15/91