Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
mgettydefs(4)
Edit
PageHistory
Diff
Info
LikePages
mgettydefs !!!mgettydefs NAME DESCRIPTION EXAMPLES FILES SEE ALSO ---- !!NAME mgettydefs - speed and terminal settings used by mgetty !!DESCRIPTION The __/etc/gettydefs__ file contains information used by mgetty(1) to set up the speed and terminal settings for a line. It also supplies information on what the ''login'' prompt should look like. Many versions of UNIX have a version of getty(1) that also reads __/etc/gettydefs__. Both ''mgetty'' and ''getty'' expect similar formats in __/etc/gettydefs__ except that, when used by ''mgetty'', extended functionality is available. Even so, the additional functions are simply ignored by standard ''getty'', so they can co-exist using the same file. Note, however, that ''mgetty'' can be compiled to use a file different from __/etc/gettydefs__ if your ''getty'' gets upset about the extensions. This manual page documents __/etc/gettydefs__ and describes the extended functionality available when used by mgetty(1). This document will refer to getty(1) except where ''mgetty'''s behaviour is different. 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 login prompt field can contain quoted characters which will be converted to other values. The sequences and their substitutions are: __n__ newline __r__ carriage return __g__ beep __b__ backspace __v__ vertical tab (VT) __f__ formfeed __t__ tab __L__ portname __C__ time in ctime(3) format. __N__ number of users currently logged in __U__ number of users currently logged in __D__ date in DD/MM format __T__ time in hh:mm:ss format __I__ modem CONNECT attributes __sequence__ where Note that standard ''getty'' usually only supports b, r and n. 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'' understands are the ones listed in termio(7)). ''mgetty'' is usually compiled for termios(7) and often has a more complete set than ''getty''. Normally only the speed flag is required in the ''initial-flags''. ''getty'' automatically sets the terminal to raw input mode and takes care of the other flags. If the mgetty(1) the speed setting is ignored. The ''initial-flag'' settings remain in effect until ''getty'' executes login(1). ''final-flags'' These flags take the same values as the ''initial-flags'' and are set just before ''getty'' executes ''login''. The speed flag is again required, except with ''mgetty'' if the -s flag was supplied. Two other 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 (a space, tab or new-line) is ignored, they are included in the ''login-prompt'' field. This field is ignored if the mgetty(1). ''next-label'' specifies the label to use if the user user types a '''' character, or ''getty'' detects a reception error. ''Getty'' searches 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__. ''next-label'' is ignored with mgetty(1). Several additional composite settings are available for ''initial-flags'' and ''final-flags''. The following composite flags are supported by ''mgetty'' and are usually supported by ''getty'': __SANE__ equivalent to ``stty sane''. (BRKINT, IGNPAR, ISTRIP, ICRNL, IXON, OPOST, CS8, CREAD, ISIG, ICANON, ECHO, ECHOK) __ODDP__ Odd parity (CS7, PARENB, PARODD) __PARITY__,__EVENP__ even parity (CS7, PARENB) __-ODDP__,__-PARITY__,__-EVENP__ no parity (resets PARENB, PARODD, and sets CS8) __RAW__ raw I/O (no canonical processing) (turns off OPOST, ICANON) __-RAW__,__COOKED__ enable canonical processing (turns on OPOST, ICANON) __NL__ Ignore newlines. (ICRNL, ONLCR) __-NL__ Respect newlines (turns INLCR, IGNCR, ICRNL, ONLCR, OCRNL, ONLRET off) __LCASE__ Ignore case - treat all as lowercase. (IUCLC, OLCUC, XCASE) Is set if mgetty believes login is entirely uppercase. __-LCASE__ Repect case (turns off IUCLC, OLCUC and XCASE) __TABS__ output tabs as tabs __-TABS__,__TAB3__ output tabs as spaces __EK__ Sets VERASE to __mgetty'' defaults VERASE to backspace.) Additionally, ''mgetty'' (but not ''getty'') can set any of the control characters listed in the __c_cc__ termio(termios) structure by the use of two tokens: Eg: VERASE ^h The value can be set as ``^ See the termio(7) or termios(7) manual pages to a list of which ``V'' variables can be changed. Note that many of these can be changed in the c_cc array, but won't have any effect. If ''getty'' is called without a second argument, the first entry of __/etc/gettydefs__ is used by ''getty'', thus making the first entry of __/etc/gettydefs__ the default entry. It is also used if ''getty'' cannot find the specified ''label''. ''Mgetty'' use a default label of ``n'', but this can be changed in the configuration. If __/etc/gettydefs__ itself is missing, there is one entry built into the command which brings up a terminal at __300__ (configuration parameter in ''mgetty'') 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. !!EXAMPLES The following two lines show an example of 300/1200 baud toggle, which is useful for dial-up ports: 1200# B1200 HUPCL # B1200 SANE IXANY TAB3 #login: #300 300# B300 HUPCL # B300 SANE IXANY TAB3 #login: #1200 The following line shows a typical 9600 baud entry for a hard-wired connection (not currently supported for ''mgetty''): 9600# B9600 # B9600 SANE IXANY IXANY ECHOE TAB3 #login: #9600 The following line is a typical smart-modem setup, suitable for ''mgetty'': 19200mg# B19200 # B19200 SANE VERASE b VINTR 003 HUPCL # nD T N Users @!login: #19200mg !!FILES /etc/gettydefs !!SEE ALSO mgetty(8), getty(8), login(1), ioctl(2), termio(7), termios(7). ----
2 pages link to
mgettydefs(4)
:
Man4m
mgetty(8)
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
