GETTY(1m) GETTY(1m)

NNAAMMEE
getty - sets terminal mode, speed, and conditions port
SSYYNNOOPPSSIISS
//ssbbiinn//ggeettttyy [-d _d_e_f_a_u_l_t_s___f_i_l_e ] [-C _c_o_n_n_e_c_t___s_c_r_i_p_t ] [-D _d_e_b_u_g___v_a_l_u_e ]
[-R] [-a] [-h] [-r _d_e_l_a_y ] [-t _t_i_m_e_o_u_t ] [-w _w_a_i_t_f_o_r ] ppoorrtt _[_s_p_e_e_d
_[_t_y_p_e _[_l_i_n_e_d_]_]_]
//ssbbiinn//ggeettttyy --cc _g_e_t_t_y_d_e_f_s___f_i_l_e
DDEESSCCRRIIPPTTIIOONN
_G_e_t_t_y is the second in the series of programs ( _i_n_i_t(1m), _g_e_t_t_y(1m),
_l_o_g_i_n(1m), and shell [bash, sh, or others]), used by the system to con
nect the user to the system (i.e., allow the user to login and thus
gain access to system resources). Note that _t_e_l_n_e_t has it's own login
process and does not use _g_e_t_t_y_. _G_e_t_t_y is invoked by _i_n_i_t(1m) to:
1. Open the tty port (usually a serial port) and condition the port (by
setting its modes);
2. Print the login prompt, and get the user's name;
3. Initiate a login process for the user (which prompts the user for
the password and validates it).
_G_e_t_t_y has many extremely convenient features, for both direct connect
devices, as well as modems, such as:
1 Conditioning the port is done by changing the stty attributes
associated with that port. Any attribute settable with stty can
be used to condition the port, including enabling or disabling
modem controls, hardware flow-control or software flow-control,
and setting 7 or 8 data bits and odd, even, mark or space par
ity;
2 Allows a multiple-use port for inbound and/or outbound connec
tions - data and fax;
3 Allows extensive prompt substitution, for custom login banners
and login prompts.
4 Auto-baud detects under a variety of conditions.
5 Optionally uses an alternate //eettcc//iissssuuee file, or does not issue
a login banner;
6 Optionally uses the //eettcc//ttttyyttyyppee file, or the tty type can be
set from the command line (the former is a nice feature if you
want others to be able to change terminal types, but don't want
to give them access to //eettcc//iinniittttaabb );
7 Optionally invokes an alternate login program, instead of the
default //bbiinn//llooggiinn ;
8 Supports ringback, if desired.
The actual procedure that _g_e_t_t_y uses is as follows:
Initially, _g_e_t_t_y parses its command line. If no errors are found, and
the tty type from the command line is set to "unknown" (the default
value), or not set, _g_e_t_t_y checks for the tty type in //eettcc//ttttyyttyyppee if
the program was compiled with _T_T_Y_T_Y_P_E defined. If a tty type is found,
either on the command line or in the //eettcc//ttttyyttyyppee file, then it is
placed into the TERM environment variable. Next, _g_e_t_t_y scans the
defaults file, normally //eettcc//ddeeffaauulltt//ggeettttyy,, to determine certain run
time values (/etc/conf.getty if compiled with FSSTND option). The val
ues in the defaults file (whose compiled-in name can be altered with
the optional --dd _d_e_f_a_u_l_t_s___f_i_l_e argument) take precedence to those on the
command line. _G_e_t_t_y then opens the _p_o_r_t for reading and writing, and
disables stdio buffering. If an initialization was specified, it is
performed (see LINE INITIALIZATION).
After the initialization, the port is closed and reopened. This time,
however, the port is opened in blocking mode so that the device is not
tied up. Detection of the carrier signal will allow the port to be
opened.
Next, _g_e_t_t_y displays the issue (or login banner, usually from
//eettcc//iissssuuee) if configured to do so, and login prompt. Finally, _g_e_t_t_y
reads the user's login name and invokes _l_o_g_i_n(1m) (or another program,
if configured) with the user's name as an argument. While reading the
name, _g_e_t_t_y attempts to adapt the system to the speed of the terminal
being used, and also sets certain terminal parameters (see _t_e_r_m_i_o_s(3))
to conform with the user's login procedure.
CCOOMMMMAANNDD AARRGGUUMMEENNTTSS
The tty device used by _g_e_t_t_y is determined by the _p_o_r_t argument. _G_e_t_t_y
uses the string //ddeevv//_p_o_r_t as the name of the device to attach itself
to.
The _s_p_e_e_d argument, if present, is used as a label to find an entry in
the //eettcc//ggeettttyyddeeffss file (see _g_e_t_t_y_d_e_f_s(4)). This entry defines to
_g_e_t_t_y the initial speed (baud rate) and tty settings, the login prompt
to be used, the final speed and tty settings, and a pointer to another
entry to try should the user indicate that the speed is not correct.
This is indicated by sending a _<_b_r_e_a_k_> character (actually sequence).
Under certain conditions, a carriage-return will perform the same func
tion. This is usually the case when getty is set to a higher speed
than the modem or terminal. _G_e_t_t_y scans the gettydefs file sequen
tially looking for a matching entry. If no _s_p_e_e_d was given or the
entry cannot be found, the first entry in the //eettcc//ggeettttyyddeeffss file is
used as a default. In the event that the gettydefs file cannot be
accessed, there is a compiled-in default entry that is used.
The optional _t_y_p_e argument is a string which identifies the type of
terminal attached to the port. This _t_y_p_e should be a valid terminal
name listed in the tteerrmmccaapp(7) database. _G_e_t_t_y uses this value to
determine how to clear the video display. It also sets the environment
variable TERM to this value, which is exported thru _l_o_g_i_n(1m) to the
shell. If this argument is not present and getty was compiled with
TTYTYPE enabled, then the terminal type is looked up in the tty type
file, usually named //eettcc//ttttyyttyyppee and the corresponding ttyyppee from there
is used.
The _l_i_n_e_d argument is a string describing the line discipline to use on
the port. The default is LLDDIISSCC00.
The name of the defaults file can be changed by specifying --dd
_d_e_f_a_u_l_t_s___f_i_l_e on the command line. If _d_e_f_a_u_l_t_s___f_i_l_e begins with a
slash, it is assumed to be a complete pathname of the defaults file to
be used. Otherwise, it is assumed to be a regular filename, causing
_g_e_t_t_y to use the pathname //eettcc//ddeeffaauulltt//ddeeffaauullttss__ffiillee.. or
//eettcc//ccoonnff..ddeeffaauullttss__ffiillee if compiled with FSSTND compliance.
Using --CC _c_o_n_n_e_c_t___s_c_r_i_p_t on the command line (or using CCOONNNNEECCTT==ssttrriinngg in
the defaults file) will cause _g_e_t_t_y to do a connection chat sequence.
Specifying the --DD _d_e_b_u_g___v_a_l_u_e switch on the command line (or using
DDEEBBUUGG==ddeebbuugg__vvaalluuee in the defaults file) will cause _g_e_t_t_y to log it's
progress in the log file specified at compile time, or the syslog file,
if none was specified.
Using the --RR switch on the command line (or using RRIINNGGBBAACCKK==YYEESS in the
defaults file) will cause _g_e_t_t_y to use ringback mode on this port.
The switch --aa _I_n_i_t___D_e_v_i_c_e specifed on the command line (or using IINNIITT
LLIINNEE==IInniitt__ddeevviiccee in the defaults file) will cause _g_e_t_t_y to open the
init_device and do the INIT script and WAITCHAR on this device instead
of the port specified on the command line.
Unless _g_e_t_t_y is invoked with the --hh flag (or HHAANNGGUUPP==NNOO is specified in
the defaults file), it will force a hangup on the port by setting the
speed to zero.
Giving --rr _d_e_l_a_y on the command line (or using WWAAIITTCCHHAARR==YYEESS and
DDEELLAAYY==_d_e_l_a_y in the defaults file) will cause _g_e_t_t_y to wait for a single
character from the port, and then to wait _d_e_l_a_y seconds before continu
ing. If no delay is desired, use --rr00.
Entering an argument of --tt _t_i_m_e_o_u_t on the command line (or using TTIIMMEE
OOUUTT==nnuummbbeerr in the defaults file) will cause _g_e_t_t_y to exit (which _i_n_i_t
should then respawn), if the login is not completed within timeout sec
onds (after the login name is entered). This option behaves differently
for _g_e_t_t_y and _u_u_g_e_t_t_y_. If _g_e_t_t_y is used, the counting will start after
single input from the user has been detected, whileas with _u_u_g_e_t_t_y_, the
counting will start immediately after _l_o_g_i_n(1m) has been spawned, no
matter the input from the user.
Giving --ww _w_a_i_t_f_o_r on the command line (or using WWAAIITTFFOORR==_w_a_i_t_f_o_r in the
defaults file) will cause _g_e_t_t_y to wait for the specified string of
characters from the port before continuing.
GGEENNEERRAALL OOPPEERRAATTIIOONN
As mentioned, _g_e_t_t_y displays the login prompt and then reads the user's
login name. If a null character is received, it is assumed to be the
result of the user pressing the _<_b_r_e_a_k_> key or the carriage-return key
to indicate the speed is wrong. This causes _g_e_t_t_y to locate the next
_s_p_e_e_d in the series (defined in /etc/gettydefs).
The user's name is expected to be terminated by a new-line or car
riage-return character. A carriage-return results in the system being
set to map those to new-lines (see _i_o_c_t_l(2)).
The user's name is scanned to see if it contains only upper-case char
acters. If so, the system is set to map any future upper-case charac
ters into lower-case. Note that on Linux, the shell /bin/sh does not
process this correctly.
A check option is provided for testing the gettydefs file. When _g_e_t_t_y
is invoked with the --cc_g_e_t_t_y_d_e_f_s option, it scans the named _g_e_t_t_y_d_e_f_s
file and prints out (to the standard output) the values it sees. If
any parsing errors occur (due to errors in the syntax of the gettydefs
file), they are reported.
DDEEFFAAUULLTTSS FFIILLEE
During its startup, _g_e_t_t_y looks for the file //eettcc//ddeeffaauulltt//ggeettttyy..ppoorrtt,,
(or, if it cannot find that file, then //eettcc//ddeeffaauulltt//ggeettttyy), and if
found, reads the contents for lines of the form
NAME=_v_a_l_u_e
This allows getty to have certain features configurable at runtime,
without recompiling. The recognized NAME strings, and their corre
sponding values, follows:
SYSTEM=_n_a_m_e
Sets the nodename value (displayed by @@SS -- see PROMPT SUBSTITU
TIONS) to _n_a_m_e. The default is the _n_o_d_e_n_a_m_e value returned by
the _u_n_a_m_e(3) call.
VERSION=_s_t_r_i_n_g
Sets the value that is displayed by the @@VV parameter (see PROMPT
SUBSTITUTIONS) to _s_t_r_i_n_g_. If _s_t_r_i_n_g begins with a '/' character,
it is assumed to be the full pathname of a text file, and @@VV is
set to be the contents of the first line in that file (line has
to be terminated by newline character or by end of file).
The default is /proc/version.
LOGIN=_n_a_m_e
Sets the name of the login program to _n_a_m_e_. The default is
//bbiinn//llooggiinn (see _l_o_g_i_n(1m)). If used, _n_a_m_e must be the full path
name of the program that _g_e_t_t_y will execute instead of
//bbiinn//llooggiinn. Note that this program is called, as is //bbiinn//llooggiinn,
the with the user's name as its only argument.
INIT=_s_t_r_i_n_g
If defined, _s_t_r_i_n_g is an expect/send sequence that is used to
initialize the port before _g_e_t_t_y attempts to use it. This string
is in a form resembling that used in the _L_._s_y_s file of _u_u_c_p(1).
For more details, see LINE INITIALIZATION. By default, no ini
tialization is done.
ISSUE=_s_t_r_i_n_g
During startup, _g_e_t_t_y defaults to displaying, as an issue or
login banner, the contents of the //eettcc//iissssuuee file. If ISSUE is
defined to a _s_t_r_i_n_g_, that string is displayed instead. If _s_t_r_i_n_g
begins with a '/' character, it is assumed to be the full path
name of a file, and that file is used instead of //eettcc//iissssuuee.
CLEAR=_v_a_l_u_e
If _v_a_l_u_e is NNOO, then _g_e_t_t_y will not attempt to clear the video
screen before displaying the issue or login prompts. The default
is to clear the screen.
HANGUP=_v_a_l_u_e
If _v_a_l_u_e is NNOO, then _g_e_t_t_y will NOT hangup the port during its
startup. This is analogus to giving the --hh argument on the com
mand line.
WAITCHAR=_v_a_l_u_e
If _v_a_l_u_e is YYEESS, then _g_e_t_t_y will wait for a single character from
it's port before continuing. This is useful for modem connec
tions where the modem has CD forced high at all times, to keep
getty from endlessly chatting with the modem.
DELAY=_s_e_c_o_n_d_s
Used in conjunction with WWAAIITTCCHHAARR, this adds a time delay of _s_e_c_
_o_n_d_s after the character is accepted before allowing _g_e_t_t_y to
continue. Both WWAAIITTCCHHAARR and DDEELLAAYY have the same effect as speci
fying --rr_d_e_l_a_y on the command line. If WWAAIITTCCHHAARR is given without
a DDEELLAAYY, the result is equal to having said --rr00 on the command
line. The default is to not wait for a character.
TIMEOUT=_n_u_m_b_e_r
As with the --tt _t_i_m_e_o_u_t command line argument, tells _g_e_t_t_y to exit
if no user name is accepted before the _n_u_m_b_e_r of seconds elapse
after the login prompt is displayed. With _g_e_t_t_y_, the counting
will start as soon as a single character has been entered by the
user, whileas with _u_u_g_e_t_t_y_, the counting will start immediately
after the login prompt is displayed, no matter the input from the
user.
The default is to wait indefinitely for the user name.
CONNECT=_s_t_r_i_n_g
If defined, _s_t_r_i_n_g should be an expect/send sequence (like that
for INIT) to direct _g_e_t_t_y in establishing the connection. _S_t_r_i_n_g
may be defined as DDEEFFAAUULLTT, which will substitute the built-in
string:
CONNECT\s\A\r\n
The \A escape marks the place where the digits showing the speed
will be seen. See CONNECTION AND AUTOBAUDING for more details.
The default is to not perform a connection chat sequence.
WAITFOR=_s_t_r_i_n_g
This parameter is similar to WAITCHAR, but defines a string of
characters to be waited for. _G_e_t_t_y will wait until _s_t_r_i_n_g is
received before issuing the login prompt. This parameter is best
used when combined with CONNECT, as in this example:
WAITFOR=RING
CONNECT="" ATA\r CONNECT\s\A
This would cause _g_e_t_t_y to wait for the string RRIINNGG, then expect
nothing, send AATTAA followed by a carriage-return, and then wait
for a string such as CCOONNNNEECCTT 22440000, in which case, _g_e_t_t_y would set
itself to 2400 baud. The default is not to wait for any string
of characters.
ALTLOCK=_p_o_r_t
_U_u_g_e_t_t_y uses this parameter to lock an alternate device, in addi
tion to the one it is attached to. This is for those systems
that have two different device names that refer to the same phys
ical port; e.g. /dev/tty1A vs. /dev/tty1a, where one uses modem
control and the other doesn't. See the section on UUGETTY for
more details. The default is to have no alternate lockfile.
ALTLINE=_p_o_r_t
_G_e_t_t_y uses this parameter to specify a different device to use
for handling modem initialization. If the WAITFOR option is
being used, WAITFOR will be done on this port also. This is nec
essary for systems that exercise locking between two ports.
RINGBACK=_v_a_l_u_e
If _v_a_l_u_e is _Y_E_S ringback callin is enabled. This is used in con
junction with _W_A_I_T_F_O_R and _C_O_N_N_E_C_T to negotiate incoming calls.
The default action is to connect only if the line rings one to
three times, is hung up, and is called back within 60 seconds of
the first call. _M_I_N_R_B_T_I_M_E and _M_A_X_R_B_T_I_M_E specify the minimum and
maximum time for the second call. _I_N_T_E_R_R_I_N_G specifies the maxi
mum time between two successive rings in the same call. _M_I_N_R_I_N_G_S
and _M_A_X_R_I_N_G_S specify the minimum and maximum number of rings for
the first call.
SCHED=_r_a_n_g_e_1 _r_a_n_g_e_2 _r_a_n_g_e_3 _._._.
_G_e_t_t_y uses this line to schedule times to allow logins. Each
range has the form DOW:HR:MIN-DOW:HR:MIN. DOW is the day of the
week. 0 = Sunday, 1 = Monday, ... 6 = Saturday. HR is the hour,
and MIN is the minute. If the current time falls into one of
these ranges, the INIT sequence (if any) is sent and _g_e_t_t_y con
tinues to run until the off time. Otherwise, the OFF sequence is
sent, and getty sleeps until the on time.
OFF=_s_t_r_i_n_g
This line is identical to the INIT line, except it is only sent
when the port is scheduled to be OFF.
FIDO=_s_t_r_i_n_g
This line specifies the path to the FidoNet mailer (usually
ifcico). Undefined by default. When setting up a FidoNet
mailer, you should also set EMSI to _y_e_s. When an incoming
FidoNet call is received, the string _t_s_y_n_c or _y_o_o_h_o_o is passed to
the FidoNet mailer as the only command line option if two TSYNC
or two YOOHOO sequences are received. If EMSI is set to _y_e_s, the
entire EMSI string (starting with the first asterisk, and up to
but not including the final carraige return) is passed as the
only command line option.
EMSI=_v_a_l_u_e
If set to _y_e_s, scan the input for FidoNet EMSI sequences.
PPRROOMMPPTT SSUUBBSSTTIITTUUTTIIOONNSS
When _g_e_t_t_y is displaying the issue or login banner (ususally
//eettcc//iissssuuee), or the _l_o_g_i_n_-_p_r_o_m_p_t_, it recognizes several escape (quoted)
characters. When one of these quoted characters is found, its value is
substituted in the output produced by _g_e_t_t_y_. Recognized escape charac
ters are:
\\ Backslash (\).
\b Backspace (^H).
\c Placed at the end of a string, this prevents a new-line from
being displayed after the string.
\f Formfeed (^L).
\n New-line (^J).
\r Carriage-return (^M).
\s A single space (' ').
\t Horizontal tab (^I).
\_n_n_n Outputs the ASCII character whose decimal value is _n_n_n. If _n_n_n
begins with 0, the value is taken to be in octal. If it begins
with 0x, the value is taken to be in hexidecimal.
In addition, a single backslash at the end of a line causes the immedi
ately following new-line to be ignored, allowing continuation lines.
Also, certain @@_c_h_a_r parameters are recognized. Those parameters, and
the value that is substituted for them are:
@B The current (evaluated at the time the @@BB is seen) baud rate.
@D The current date, in MM/DD/YY .
@F The Fully Qualified Domain Name (FQDN) of the system.
@L The _p_o_r_t (serial line) to which _g_e_t_t_y is attached.
@M The architecture identifier of the machine ("i386", for example).
@O The Operating System name of the system ("Linux", for example).
@R The operating system release identifier of the system ("2.4.5",
for example).
@S The system node name.
@T The current time, in HH:MM:SS (24-hour) .
@U The number of currently signed-on users. This is a count of the
number of entries in the _/_e_t_c_/_u_t_m_p file that have a non-null
ut_name field.
@V The value of VVEERRSSIIOONN, as given in the defaults file.
@u The value "1 user" or "<n> users", where <n> is the number of
currently signed-on users. <n> is computed like "@U", above.
To display a single '@' character, use either '\@' or '@@'.
LLIINNEE IINNIITTIIAALLIIZZAATTIIOONN
One of the greatest benefits (in the author's opinion, at least) is the
ability of _g_e_t_t_y to initialize its port before use. This will most
likely be done on ports with modems, not terminals, although initializ
ing terminals is not out of the question.
Port initialization is performed just after the _p_o_r_t is opened and
prior to handling the WAITCHAR and/or WAITFOR options. Initialization
is accomplished by placing an
INIT=_s_t_r_i_n_g
line in the defaults file. _S_t_r_i_n_g is a series of one or more fields in
the form
expect [ send [ expect [ send ] ] ... ]
This resembles the expect/send sequences used in the UUCP _L_._s_y_s file,
with the following exception: A carriage return is NOT appended auto
matically to sequences that are 'sent.' If you want a carriage-return
sent, you must explicitly show it, with '\r'.
_G_e_t_t_y supports subfields in the expect field of the form
expect[-send-expect]...
as with UUCP. All the escape characters (those beginning with a '\'
character) listed in the PROMPT SUBSTITUTIONS section are valid in the
send and expect fields. In addition, the following escape characters
are recognized:
\p Inserts a 1-second delay.
\d Inserts a 2-second delay.
\K Sends a .25-second Break.
\T_n_n_n Modifies the default timeout (usually 30 seconds) to the value
indicated by _n_n_n. The value _n_n_n may be decimal, octal, or hex
idecimal; see the usage of \\_n_n_n in PROMPT SUBSTITUTIONS.
Note that for these additional escape characters, no actual character
is sent.
CCOONNNNEECCTTIIOONN AANNDD AAUUTTOOBBAAUUDDIINNGG
_G_e_t_t_y will perform a chat sequence establish a proper connection. The
best use of this feature is to look for the CCOONNNNEECCTT message sent by a
modem and set the port speed to the number given in that message (e.g.
CONNECT 2400). Note that for modern modems, it makes much more sense
to leave the serial port at a fixed baud (normally the highest sup
ported by the modem), and have the modem data speed (i.e., the speed
over the phone line) vary. That way, you are always assured of the
maxumum transfer rate. (Because, the modems will connect at the high
est common baud rate, subject to phone line quality; if the serial port
is faster, then the flow control will regulate the data flow between
the modems.)
The structure of the connect chat script is exactly the same as that
for the INIT script (see LINE INITIALIZATION), with the following addi
tion:
\A Marks the spot where the baud rate will be seen. This mark will
match any and all digits 0-9 at that location in the script, and
set it's speed to that value, if possible.
Autobauding, therefore, is enabled by placing the 00
CONNECT=CONNECT\s\A
would match the string CCOONNNNEECCTT 11220000 and cause _g_e_t_t_y to set it's baud
rate to 1200, using the following steps:
1. Having matched the value 1200, _g_e_t_t_y will attempt to find an entry
with the label 11220000 in the ggeettttyyddeeffss file. If a matching gettydefs
entry is found, those values are used. If there is no match, then
2. The gettydefs values currently in use are modified to use the
matched speed (e.g. 1200). However, if the matched speed is
invalid, then
3. _G_e_t_t_y logs a warning message and resumes normal operation. This
allows the practice of toggling through linked entries in the getty
defs file to behave as expected.
UUUUGGEETTTTYY
_U_u_g_e_t_t_y has identical behavior to _g_e_t_t_y_, except that _u_u_g_e_t_t_y is
designed to create and use the lock files maintained by the UUCP family
_(_u_u_c_p(1), _c_u(1) and others). This prevents two or more processes from
having conficting use of a tty port.
_U_u_g_e_t_t_y also differs from _g_e_t_t_y by handling the -t parameter and TIME
OUT option.
When _u_u_g_e_t_t_y starts up, if it sees a lock file for the port it intends
to use, it will use the pid in the lock file to see if there is an
active process holding the lock. If not, _u_u_g_e_t_t_y will remove the lock
file and continue. If a valid process is found, _u_u_g_e_t_t_y will sleep
until that process releases the lock and then it will exit, forcing
_i_n_i_t(1m) to spawn a new _u_u_g_e_t_t_y_. Once no conflicting process is found,
_u_u_g_e_t_t_y grabs the _p_o_r_t by creating the lock file itself before issuing
the login prompt. This prevents other processes from using the port.
_U_u_g_e_t_t_y will normally only lock the name of the port it is running on.
On systems where there are two device names referring to the same port
(as is the case where one device uses modem control while the other
doesn't), place a line of the form
ALTLOCK=_p_o_r_t
line in the defaults file. For instance, if _u_u_g_e_t_t_y is on _/_d_e_v_/_t_t_y_1_a_,
and you want to have it lock _/_d_e_v_/_t_t_y_1_A also, use the line AALLTT
LLOOCCKK==ttttyy11AA in the defaults file. Note that on Linux (after kernel
2.0.0 or so), the use of the non-modem port "cuax" is discouraged.
Uugetty is set up to work with only the modem-control "ttySx" port, by
exact use of permissions and ownership of the port (owned by user
UUCP), in conjunction with suid. Other programs wishing to share a
modem port with uugetty should work well if they also are owned by uucp
and have the suid bit set on their executable (plus whatever additional
permissions issues need resolving).
Note that uugetty will work not only with modems, but also with a
direct serial connection between two machines. This would allow a
fairly secure file transfer channel between two machines. I have
acheived throughput in excess of 115200 baud between two systems with a
short serial cable (10 feet or so).
While waiting for carrier detect, _U_u_g_e_t_t_y will check for lockfiles
every 30 seconds. If lockfiles are found, uugetty will exit, and init
will respawn another _g_e_t_t_y_. This allows the modem to be reinitialized
after another process has used the modem.
FFIILLEESS
/etc/default/getty[_._p_o_r_t]
Contains the runtime configuration. Note that _u_u_g_e_t_t_y
uses /etc/default/uugetty[_._p_o_r_t].
/etc/gettydefs Contains speed and tty settings to be used by _g_e_t_t_y_.
/etc/ttytype Contains TERM value to be passed to the shell (if not
present on the command line), associated by port ID.
/etc/issue The default issue (or login banner), if any.
/bin/login The default login program called after the user's name
is entered.
SSEEEE AALLSSOO
init(1m), login(1m), uucp(1), ioctl(2), uname(3), gettydefs(5),
issue(5), utmp(5), termios(3)
AAUUTTHHOORRSS
Getty_ps in its current magical form:
Christine Jamison <getty-info@nwmagic.net>
Original getty_ps:
Paul Sutcliffe, Jr. <paul@devon.lns.pa.us>
UUCP: ...!rutgers!devon!paul
Autobauding routines adapted from code submitted by
Mark Keating <...!utzoo!censor!markk>
And numerous patches and assistance supplied by various helpful people!
Release 2.1.0 12-Sep-02 GETTY(1m)