System Administration Guide
Chapter 7, Connecting to other computers with UUCP

Troubleshooting UUCP

Troubleshooting UUCP

Before troubleshooting the UUCP system, make sure that the physical connection works. If you are connecting to UUCP with a modem, verify that the modem is installed and configured correctly. See ``Troubleshooting modems'' in the SCO OpenServer Handbook. If you are using a direct line, make sure that the computers are connected correctly -- use the instructions in ``Connecting two local systems using a direct wire''.


NOTE: If you are configuring an outbound UUCP connection over a modem, cu must function for UUCP to work.

If the hardware is correctly configured but a session is repeatedly failing for no known reason, the first troubleshooting step should be to run uutry and save the output log. The log (stored in /tmp/hostname, where hostname is the remote host's name) contains a listing of the steps uucico went through, and may indicate where the failure occurred.

uucico produces 11 levels of debugging output, from 0 to 10. Level 9 is the most verbose standard mode, and is generated when uucico receives the command line option -x9 (you can also pass this option to uutry when testing the uucico connection to a given site). Level 10 is identical to level 9, except that the output from the ``g'' or ``G'' protocols is written to a file in /tmp for future reference.

See also: