Setting Up UUCP on a TCP/IP Connection

Setting Up UUCP on a TCP/IP Connection

In many cases, you may decide to use the UUCP tools over conventional TCP/IP network connections. There are entries in the Devices file provided for this, but you must make some changes in the /usr/etc/inetd.conf and /etc/uucp/Systems files. Follow these steps:

Edit the /usr/etc/inetd.conf file on the remote host and find this line:
#uucp stream tcp nowait root /usr/lib/uucp/uucpd uucpd
Remove the leading hashmark (#) to uncomment the line, and use these commands to make the change take effect:

/etc/init.d/network stop
/etc/init.d/network start
This change tells the remote system to run the uucpd daemon when a request comes in for UUCP transfer.
Add a line similar to the following to your local /etc/uucp/Systems file:
remotehost Any TCP Any
The name remotehost should be replaced with the name of the remote host you will be calling.
Run the /etc/uucp/genperm command as root on the local host to generate the UUCP Permissions file.
Enter the following command to check that everything is set up correctly:
/usr/lib/uucp/uucheck -v
There is a great deal of output. You should see output similar to the following for the specific entry you made:

When we call system(s): (remotehost)
We DO allow them to request files.
They can send files to
/var/spool/uucppublic (DEFAULT)
They can request files from
/var/spool/uucppublic
/usr/lib/mail
/usr/people/ftp
Myname for the conversation will be MyName.
PUBDIR for the conversation will be /var/spool/uucppublic.

Machine(s): (remotehost)
CAN execute the following commands:
command (rmail), fullname (/bin/rmail)
command (rnews), fullname (/usr/bin/rnews)
command (cunbatch), fullname (/usr/lib/news/cunbatch)

The cu command does not work for UUCP over a TCP connection. Use the /usr/lib/uucp/Uutry command instead. Uutry is documented completely in the Uutry(1M) reference page and in "Testing With Uutry".