UUCP keeps track of activity in log and status files in the /usr/spool/uucp directory. The UUCP programs uucp, uux , uucico , and uuxqt write status information for each system to files in the /usr/spool/uucp/.Log directories. The uucico utility writes messages to the files in the /usr/spool/uucp/.Status directory. These messages describe the status of the transfer request, such as uucico failures, completions, and the time until the next allowable call for each remote system with which you communicate.
The following sections suggest responses to common error messages that UUCP programs write to these files.
The uucico creates a lock file named LCK..sitename for the remote system in the /usr/spool/uucp directory. If a file for the system that you are trying to call exists, uucico assumes that the device is in use.
To use the device, enter the following command on the
remote system, substituting the name of the
remote system for sitename:
If this error message appears, one of several things may be wrong:
If the system displays this message, one of several things may be wrong:
If the system displays this message, the /usr/lib/uucp/Systems file on the machine that you are trying to call does not contain an entry for your machine. Check the Systems file on the remote machine.
If your system displays this message, either the remote system is trying to call your system or there is a lock file for your system on the remote system.
If the /usr/lib/uucp/Systems file on your system does not contain an entry for the system that you are trying to access, this error message is displayed. Use the uuname command to verify that the system name is in the Systems file.
When UUCP requests fail, retries are not executed immediately. After an attempt to contact a remote system, a status file remains in /usr/spool/uucp/.Status/nodename (nodename is the name of the remote system that you are trying to reach). This file contains information about the last request and does not allow another request until the minimum retry period (specified in the /usr/lib/uucp/Systems file) is reached. If you try to use UUCP again, the system displays an error message like the following:
RETRY TIME NOT REACHEDTo enable another call attempt immediately, remove the status file for the remote system from the /usr/spool/uucp/.Status directory:
If the system displays this message,
it cannot access the calling device port.
Check the permissions and ownership on the device file:
Where xx is the tty number. The ownership and permissions settings should look like the following:
crw-r--r-- 1 uucp uucp 5, 0 Feb 14 12:00 /dev/ttyxxSee ``Connect failed: CANNOT ACCESS DEVICE'' for information on changing the permissions.
The /usr/lib/uucp/Systems file may restrict outgoing calls at this time.