NAME

uugetty − set terminal type, modes, speed, and line discipline

SYNOPSIS

/usr/lib/uucp/getty [ −h ] [ −t timeout ] [ −r ] line
[ speed [ type [ linedisc ] ] ]
/usr/lib/uucp/getty −c file

DESCRIPTION

uugetty is identical 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.  Note that in the −r case, 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 an intelligent modem or 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 or direct line:

30:2:respawn:/usr/lib/uucp/uugetty −r −t 60 tty12 1200

FILES

/etc/gettydefs
/etc/issue

SEE ALSO

ct(1C), cu(1C), getty(1M), gettydefs(4), init(1M), inittab(4), ioctl(2), login(1), tty(7), uucico(1M). 

BUGS

Ct will not work when uugetty is used with an intelligent modem such as penril or ventel. 

March 13, 1992