OK

Status is okay. 

NO DEVICES AVAILABLE

There is currently no device available for the call. Check to see that there is a valid device in the Devices file for the particular system. Check the Systems file for the device to be used to call the system.

WRONG TIME TO CALL

A call was placed to the system at a time other than what is specified in the Systems file.

TALKING

Self-explanatory.  

LOGIN FAILED

The login for the given machine failed. It could be a wrong login or password, wrong number, a very slow machine, or failure in getting through the Dialer-Token-Pairs script.  

CONVERSATION FAILED

The conversation failed after successful startup. This usually means that one side went down, the program aborted, or the line (link) was dropped.  

DIAL FAILED

The remote machine never answered. It could be a bad dialer or the wrong phone number.  

BAD LOGIN/MACHINE COMBINATION

The machine called us with a login/machine name that does not agree with the Permissions file. This could be an attempt to masquerade!.

DEVICE LOCKED

The calling device to be used is currently locked and in use by another process.  

ASSERT ERROR

An ASSERT error occurred. Check the /var/uucp/.Admin/errors file for the error message and refer to the section "UUCP Error Messages".

SYSTEM NOT IN Systems FILE

The system is not in the Systems file.

CAN'T ACCESS DEVICE

The device tried does not exist or the modes are wrong. Check the appropriate entries in the Systems and Devices files.

DEVICE FAILED

The device could not be opened.  

WRONG MACHINE NAME

The called machine is reporting a different name than expected.  

CALLBACK REQUIRED

The called machine requires that it calls your machine.  

REMOTE HAS A LCK FILE FOR ME

The remote machine has a LCK file for your machine. It could be trying to call your machine. If it has an older version of UUCP, the process that was talking to your machine might have failed, leaving the LCK file. If it has the new version of UUCP and is not communicating with your machine, then the process that has a LCK file is hung.

REMOTE DOES NOT KNOW ME

The remote machine does not have the node name of your machine in its Systems file.

REMOTE REJECT AFTER LOGIN

The login used by your machine to login does not agree with what the remote machine was expecting.  

REMOTE REJECT, UNKNOWN MESSAGE

The remote machine rejected the communication with your machine for an unknown reason. The remote machine might not be running a standard version of UUCP.  

STARTUP FAILED

Login succeeded, but initial handshake failed.  

CALLER SCRIPT FAILED

This is usually the same as DIAL FAILED. However, if it occurs often, suspect the caller script in the Dialers file. Use Uutry to check.