UUGETTY(1M) UUGETTY(1M)
uugetty - set terminal type, modes, speed, and line discipline
/usr/lib/uucp/uugetty [-hNDr] [-t timeout] [-d delay]
[-i chat1,[chat2]] line [speed [type [linedisc]]]
/usr/lib/uucp/uugetty -c file
uugetty is similar to getty(1M), but changes have been made to support
using the line for uucico, cu, and ct; that is, the line can be used in
both directions. The uugetty will allow users to login, but if the line
is free, uucico, cu, or ct can use it for dialing out. The
implementation depends on the fact that uucico, cu, and ct create lock
files when devices are used. When the "open()" returns (or the first
character is read when -r option is used), the status of the lock file
indicates whether the line is being used by uucico, cu, ct, or someone
trying to login.
The -d option specifies a number of seconds to wait after the first
character is available from the line, and then to discard all input.
This option can be useful with modems which provide 'call progress'
information when answering. For example, the -d option can be used to
ignore 'RING' and 'CONNECT' which would otherwise fool uugetty into
invoking login before the correct speed has been determined. When
possible, two chat-scripts should be used with -i option instead.
The -i option specifies one or two "chat-script" entries in
/etc/uucp/Dialers. Uugetty uses the first chat-script before going to
sleep to wait for the first input. This should be used to tell a modem
to answer the telephone the next time it rings. The modem can be
configured to not answer until uugetty is ready to answer.
The second chat-script used with -i can be used to wait for the modem to
say the connection is completely established. This allows stray 'RING'
messages or long modem protocol negotiations to be ignored gracefully.
-N option honors the /etc/nologin file. When present, uugetty does not
answer the line, but instead waits for the file to go away.
Unless uugetty is invoked with the -h flag, uugetty will force a hangup
on the line by setting the speed to zero before setting the speed to the
default or specified speed. The -t flag plus timeout (in seconds),
specifies that uugetty should exit if the open on the line succeeds and
no one types anything in the specified number of seconds.
The -D option turns on uucico debugging, with the output sent to the
system log, /var/adm/SYSLOG. It can be useful for testing a script
specified with the -i option.
Page 1
UUGETTY(1M) UUGETTY(1M)
Note that when the -r option is used, several <carriage-return>
characters may be required before the login message is output. The human
users will be able to handle this slight inconvenience. Uucico trying to
login will have to be told by using the following login script:
"" \r\d\r\d\r\d\r in:--in: ...
where the ... is whatever would normally be used for the login sequence.
An entry for direct line that has a uugetty on each end must use the -r
option. This causes uugetty to wait to read a character before it puts
out the login message, thus preventing two uugettys from looping. If
there is a uugetty on one end of a direct line, there must be a uugetty
on the other end as well.
Here is an /etc/inittab entry using uugetty on an intelligent modem:
t5:23:respawn:/usr/lib/uucp/uugetty -Nt 60 -itelebitin,conn ttyf5 dx_19200
Note that a /etc/gettydefs entry which cycles among the speed(s)
appropriate for the modem should be chosen. Modems which "lock" to a
single speed, such as most high speed modems, should be used with a
gettydefs entry which sticks to a single speed, such as dx_19200.
When uugetty is invoked with the -c option and file, it scans the file as
if it were scanning /etc/gettydefs during normal operation, and prints
out the results to the standard output. If there are any unrecognized
modes or improperly constructed entries, it reports these. If the
entries are correct, it prints out the values of the various flags. See
ioctl(2) to interpret the values. Note that some values are added to the
flags automatically.
/etc/nologin
/etc/gettydefs
/var/adm/SYSLOG
/etc/uucp/Dialers
/etc/issue
login(1), cu(1C), getty(1M), init(1M), uucico(1M), ioctl(2),
gettydefs(4), inittab(4), duart(7), tty(7)
Most error messages are sent to the system log, /var/adm/SYSLOG.
PPPPaaaaggggeeee 2222 [ Back ]
|
