HP-UX Reference (11i v2 07/12) - 1M System Administration Commands A-M (vol 3)

g
getty(1M) getty(1M)
Operation
When given no optional arguments, getty sets the speed of the interface to 300 baud, specifies that raw
mode is to be used (awaken on every character), that echo is to be suppressed, that either parity is to be
allowed, that newline characters are to be converted to carriage-return-linefeed, and that tab expansion is
to be performed on standard output. It types the login message before reading the user’s name a character
at a time. If a null character (or framing error) is received, it is assumed to be the result of the user push-
ing the break key. This causes
getty to attempt the next speed in the series. The series that
getty
tries is determined by what it finds in
/etc/gettydefs.
The user’s name is terminated by a newline or carriage-return character. The latter results in the system
being set to treat carriage returns appropriately (see ioctl(2)).
The user’s name is scanned to see if it contains any lowercase alphabetic characters; if not, and if the name
is nonempty, the system is told to map any future uppercase characters into the corresponding lowercase
characters.
getty also understands the "standard" ESS2 protocols for erasing, killing and aborting a line, and ter-
minating a line. If getty sees the ESS erase character (
_), or kill character ($), or abort character (&), or
the ESS line terminators (
/ or
!), it arranges for this set of characters to be used for these functions.
With the
-f option, getty obtains the special control characters for the terminal from the
/dev/ttyconf file. This terminal setting will be inherited by login.
Finally, login is called with the user’s name as an argument. Additional arguments can be typed after
the login name. These are passed to login, which places them in the environment (see login(1)).
Check Option
A check option is provided. When
getty is invoked with the -c file option, it scans file as if scanning
/etc/gettydefs and prints the results on standard output. If there are any unrecognized modes or
improperly constructed entries,
getty reports these. If the entries are correct, getty prints out the
values of the various flags. See ioctl(2) for an interpretation of values. Note that some values are added to
the flags automatically.
WARNINGS
While getty does understand simple single character quoting conventions, it is not possible to quote the
special control characters that getty uses to determine when the end of the line has been reached, which
protocol is being used, and what the erase character is.
DEPENDENCIES
HP2334 MultiMux
The modem control parameter MRTS must be present in the /etc/gettydefs
file when using getty
in conjunction with an HP2334 or HP2335 MultiMux to ensure that the RTS modem control signal is
asserted correctly.
Example:
9600# B9600 HUPCL PARENB MRTS # B9600 SANE PARENB ISTRIP IXANY #login: #19200
MRTS
is not intended for use with devices other than the HP2334 or HP2335 MultiMux.
FILES
/dev/ttyconf
/etc/gettydefs
/etc/issue
SEE ALSO
ct(1), login(1), stty(1), init(1M), ioctl(2), gettydefs(4), inittab(4), modem(7), termio(7).
338 Hewlett-Packard Company 2 HP-UX 11i Version 2: December 2007 Update