Additional Features added to AmigaUUCP1.16 Getty for AmigaFax
==============================================================
Additional command line parameter added.
-Fn n=bit-mapped register
bit
0 = 1 (always set for Fax)
1 = 0 Set rate to 19200 after +FCO
= 1 Don't set rate to 19200 after +FCO, DCE/DTE locked
2 = 0 Dont Open/Close serial on modem-init
= 1 Open/Close serial on modem-init
So for example, if you want to operate in Fax-Compatible mode, with
your modem having a locked DCE/DTE rate, and you want to Close/Open
the serial device between calls (for some reason this helps a lot when
using the ZyXEL modem, and the A2232 multi-port serial card), you
would add the parameter -F6 when starting Getty.
==========================================================================
This is the Getty documentation from the AmigaUUCP1.16 distribution
==========================================================================
NAME
Getty
SYNOPSIS
Getty -Sserialname -Uunit -Bbaud -Bbaud.. -Mc -bn -ln
-m1 -r0 -h0 -c0 -d0 -xn -A -7 -0 [modem-cmds]
FLASH!
Getty now works with multi-serial ports. The 1.08 and 1.09
getty were broken due to bugs in the serial.device ... the 1.10
Getty now fixes this by introducing file locking constructs to
lock the serial port instead of intercepting the device vectors.
IN ORDER TO BEHAVE WELL WITH GETTY, YOU MUST USE THE LockSerial
command to run any external programs that use that particular
serial port. You can no longer run terminal programs direct
because they are no longer locked out by getty if getty is
accepting a call. The program LOCKSERIAL may be used to
synchronously run terminal programs without requiring one to
kill Getty.
HOWEVER, programs run *FROM* a password entry should NOT use
LockSerial becaues the port has already been locked by getty
for the program.
NOTE: Programs run with lockserial must not auto-detach from the
CLI or lockserial will believe that they have exited and give the
port back to Getty, causing major problems.
DESCRIPTION
Getty hangs on the specified serial port (serial.device unit 0 by
default) waiting for connections via the connected modem. Once
a connection is accepted Getty adjusts to the proper baud rate
using the CONNECT message, -B, -A options, then provides a
Login: request to the caller.
NOTE: A CONNECT message from the modem with no baud rate specified
will cause Getty to use the first baud rate in the -B list. If
the -A option is specified, Getty *always* uses the first baud
rate in the -B list and never switches to any other baud rate.
Getty disconnects any caller who cannot provide a legal Login and
Password within 60 seconds. It also allows only 5 login attempts
before disconnecting, and any illegal password will result in a
4 second delay before the next Login: prompt is output.
Upon receiving a legal Login and and Password, verified via
GETTY:PASSWD, Getty will execute the program specified in
GETTY:PASSWD, usually UUCICO, and stay off the line until
UUCICO returns. When UUCICO returns, Getty will disconnect
the caller and reset the modem, returning to its original state.
The file GETTY:Getty-Header contains a couple lines of text
that are sent over the serial port before the Login: request.
In it you normally have your machine type, name, etc...
Getty runs the specified program in the password entry adding
the following arguments:
-Getty -DEVICE devicename -UNIT unitnumber
(uucico will recognize said arguments and not attempt to
initialize / waitfor calls / hangup the modem itself, nor
will uucico attempt to lock the already locked serial port)
TECH NOTES
In order to monitor the request lock for the serial port (see
UUMAN:LockSerial and src/util/lockserial.c), GETTY must open
a file in T: for write and then close it every 3 seconds. Thus,
T: should be in your RAM disk.
OPTIONS
Options are given on the command line when you run Getty. You can
also UPDATE a currently running Getty's options by running Getty
for the same device and unit again with the options that need to
be changed. Getty will detect whether another getty is already
running on that port and send the new options to the running getty,
then return.
-Sserialname Specify serial device, default "serial.device"
-Uunit Specify unit number, default 0
-Bbaud Specify up to 32 baud rates
-A Specify modem will adjust to a single baud
rate (locks the serial.device at the first
baud rate in the -B list)
-7 Use SERF_7WIRE protocol while online,
else uses no protocol while online. If
you are using a modem with speed conversion
you need this option or you will most likely
overflow the modem's buffer!
-Mc Select Modem type,
c = m Multimodem
h Hays
d Dumb (no AT or +++ commands are
sent to the modem ever).
-mn Set modem speaker level, default 0.
(ATMn command)
-rn Set modem to answer on the Nth ring
(modem must support ATMn). 0 disables
answer capability. The default is to
answer on the second ring.
-h0 Ignore CD (carrier detect). If this option
is specified a continuous carrier detect is
assumed, causing Getty to request Login:'s
over the line as soon as it receives a CONNECT
message.
It is suggested you ONLY use this option
when combined with -c0
-c0 Do NOT look for a CONNECT message from the
modem... useful for dumb modems.
-d0 Normally Getty will disconnect by dropping
DTR. If this option is specified, Getty will
use the less reliable +++ ATH0 sequence.
NOTE: If your modem has the capability to LOCK
the COMPUTER'S SERIAL PORT baud rate, it is
*strongly* suggested that you do this for +++
to be reliable.
-xn Set debugging level to n. If specified
debugging messages are sent to stdout instead
of GETTY:LOGFILE
Note: to avoid GETTY:LOGFILE getting too
large for busy systems, you can always add
an entry to your crontab to delete it once
a week (or whenever), or use 'trimfile' to
trim it.
-l1 add -HLINK option to commands started by
Getty.
-b1 add -BAUD <baud> option to commands started by
Getty, this informs the run command what the
actual connect baud rate is regardless of the
serial port communications baud rate (which is
already preset by getty for the application)
-0 Kill any already-running Getty for this
serial port and unit.
modem-cmds You may specify up to 16 specific commands
to be sent to the modem whenever it is
initialized (usually after a disconnect
and on startup). Each command will be
sent to the modem with a CR on the end and
a seconds delay afterwords. Example:
ATS2=.
This is useful for provided specialized
modems with the appropriate initialization
strings.
EXAMPLE
; Run a Getty for a MultiModem
run >nil: <nil: Getty -Mm -A -B19200
; Run a Getty for a Hays Modem
run >nil: <nil: Getty -Mh -B1200 -B2400
; Run a Getty for a Hays Modem and use +++ instead of DTR to
; hangup. NOTE, when using -d0 you should lock the serial port
; baud rate (if possible) or +++ may be unreliable as a hangup
; method.
run >nil: <nil: Getty -Mh -B2400 -d0
; Modify options to a Getty already running in the background
Getty -m1 ; Set speaker on during dialing
Getty -m0 ; speaker off at all times.
Getty -0 ; kill background Getty
EXAMPLE CRONTAB ENTRIES
Assuming a getty has been run in the background from your
startup sequence, the most common desire is to disable the
modem speaker while you are asleep, and enable it at other
times. The following crontab entry will accomplish this:
0 23 * * * getty -m0
0 11 * * * getty -m1
You can also kill (getty -0) or restart getty from your
crontab, though the prefered method is to leave it running
and only disable/enable the autoanswer (-r option) for those
times you wish your modem to not accept calls.
EXAMPLE HARDWIRED ENTRY
Lets say you have two amigas connected together via a permanent
serial line. To run AmigaUUCP between them you want to run Getty
on one of them (NOT BOTH!). On machine A you would run Getty
as follows:
(Machine A):
run >nil: <nil: Getty -B9600 -Md -h0 -c0
The Passwd entry for the remote machine would be something like:
(Machine A)
machb,uupc,203,0,(UUCP-NOPAS),ram:,uucico -h0 -o
Machine B would have an L.sys entry that looks like:
macha Any SER: 9600 "" "" \r\r\c ogin: machb sword: uupc
In the above configuration, with Getty running on Machine A, Machine
B would run uucico (usually every X minutes from dcron) using:
1> uucico -smacha -h0 -o -xx
UNFORTUNATELY, with a permanent serial line you cannot run Getty
on BOTH machines. This will cause one Getty to echo the other's
login message and vise versa, causing an infinite loop. So only
one machine can poll.
FILES/REQUIRES
GETTY:PASSWD
GETTY:Getty-Header
GETTY:LOGFILE
The NULL: handler must be mounted
REFERENCES
Getty
Passwd
