Digi PortServer/8 User Manual page 96

rtty -1ds /dev/ttysf dbps-nodename 2104
Note the use of the 21?? raw connect port numbers (as opposed to 20?? series telnet connect
numbers). See PortServer Port Numbers on page 101.
Add a few lines like the following to your uucp "Devices" file. All baud rates are equivalent,
since the pseudo tty device driver ignores them, but they must match up with the value given in
your "Systems" file. On some systems, the "hayes" keyword is omitted; on other systems you will
want to replace it with the name of the dialer script your modem uses.
ACU ttysc ttysc 38400 hayes
ACU ttysd ttysd 38400 hayes
ACU ttyse ttyse 38400 hayes
ACU ttysf ttysf 38400 hayes
Having done just these two things, the modems will now appear directly connected to cu and
uucp, so you should be able to test your configuration by typing something like:
cu -l /dev/ttysc -b 38400 555-1212
Depending on your system, you may need to make a few more tweaks, but the rest of it is the
same as you would encounter on any other directly connected port.
It is possible for several (or many) different computer systems on a network to configure
pseudo-ttys associated with the same port (or port group) on an PortServer. This works because
RTTY only attempts a connection when data is written to the pseudo tty. If the PortServer port is
available, the connection is made and the program accessing the port can continue. If the port is
already in use by another system the connection will fail, and RTTY will signal the application
by momentarily closing and re-opening the pseudo-tty port. This is compatible with the way
UUCP and CU work on most systems.
The RTTY program is provided on an as-is basis by Digi as a service to its customers, but
because it is tricky to configure, and usually needed only by sophisticated users, it is not covered
by our regular unlimited technical support policy. RTTY works well on most systems, but
depends too much on non-standard features of the local UNIX system to be fully supported. Digi
provides the source, internal documentation in the source, and an unlimited distribution license
when used with our products. Most customers find it valuable, but there is no guarantee of
success.
Page 88 Ÿ PortServer Terminal Server