Go backward to TCP Client.
Go up to UUCP Over TCP.
Running a TCP Server
--------------------
The `uucico' daemon may be run as a TCP server. To use the default
port number, which is a reserved port, `uucico' must be invoked by the
superuser (or it must be set user ID to the superuser, but I don't
recommend doing that).
You must define a port, either using the port file (*note port
File::.), if you are using the new configuration method, or with an
entry in `Devices' if you are using HDB; there is no way to define a
port using V2. If you are using HDB the port must be named `TCP'; a
line as shown above will suffice. You can then start `uucico' as
`uucico -p TCP' (after the `-p', name the port; in HDB it must be
`TCP'). This will wait for incoming connections, and fork off a child
for each one. Each connection will be prompted with `login:' and
`Password:'; the results will be checked against the UUCP (not the
system) password file (see Configuration File Names.).
Another way to run a UUCP TCP server is to use the BSD `uucpd'
program.
Yet another way to run a UUCP TCP server is to use `inetd'. Arrange
for `inetd' to start up `uucico' with the `-l' switch. This will cause
`uucico' to prompt with `login:' and `Password:' and check the results
against the UUCP (not the system) password file (you may want to also
use the `-D' switch to avoid a fork, which in this case is unnecessary).