DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Administering TCP/IP

Configuring UUCP over TCP/IP with the TCP socket interface

The following steps demonstrate how to configure UUCP over TCP/IP using the TCP socket interface between the systems london and thames.

  1. On both systems, verify that the file /etc/inetd.conf contains the following line (with no ``#'' character at the beginning of the line):
       uucp    stream tcp      nowait  NOLUID  /etc/uucpd uucpd
    


    NOTE: If the system you are configuring is running SCO TCP/IP Release 1.1.3, replace ``NOLUID'' with ``root'' in the above line.

    Should the program /etc/uucpd not exist, execute the following commands as root:

    ln /usr/lib/uucp/uucpd /etc/uucpd
    chmod 755 /etc/uucpd

  2. Verify that the following line is in the /etc/services file on both systems:
       uucp    540/tcp         uucpd           # uucp daemon
    

  3. Verify the configuration of the nuucp account on each host. Make sure that the shell of this account is /usr/lib/uucp/uucico, and that the account has a password on both hosts. You will probably have to set a password for the nuucp account. Use the Account Manager to confirm the account information and set a password.

  4. Add the following line to the file /usr/lib/uucp/Systems on london:
       thames Any TCP,e Any - ogin: nuucp word: password
    
    where password is the password of the nuucp account on thames.

  5. Add the following line to the file /usr/lib/uucp/Systems on thames:
       london Any TCP,e Any - ogin: nuucp word: password
    
    where password is the password of the nuucp account on london.

  6. Verify that the /usr/lib/uucp/Permissions file on london has the following entry:
       MACHINE=thames LOGNAME=nuucp \
               COMMANDS=rmail:rnews:uucp \
               READ=/usr/spool/uucppublic:/usr/tmp \
               WRITE=/usr/spool/uucppublic:/usr/tmp \
               SENDFILES=yes REQUEST=yes
    

  7. Verify that the /usr/lib/uucp/Permissions file on thames has the following entry:
       MACHINE=london LOGNAME=nuucp \
               COMMANDS=rmail:rnews:uucp \
               READ=/usr/spool/uucppublic:/usr/tmp \
               WRITE=/usr/spool/uucppublic:/usr/tmp \
               SENDFILES=yes REQUEST=yes
    

  8. Add the following line to /usr/lib/uucp/Devices on both hosts:
       TCP,e TCP       -       Any     TCP     540
    

  9. Verify that both systems are in the other's /etc/hosts file or resolvable by a name server.

  10. If you needed to change anything in step 1, shutdown and reboot the systems on which you made the changes. UUCP should then work as expected between the two systems. Each system should be able to issue requests for the opposite system.

    Note that if you alter /etc/inetd.conf while the system is running, you should force inetd to reread the configuration file by entering the following command:

    kill -1 'cat /etc/inetd.pid'

    If you fail to make inetd restart before trying to contact it, the contacting host may give a ``Connection refused'' error.


NOTE: Note that steps 3 through 7 are similar to the steps used in configuring UUCP between systems over a serial line. Also, the user names and sample Permissions files shown here are only examples and may be changed to suit the security needs of a particular site.


Next topic: Configuring UUCP over TCP/IP with TLI
Previous topic: Configuring UUCP over TCP/IP

© 2007 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 05 June 2007