CAN'T OPEN

An open() or fopen() failed.

CAN'T WRITE

A write(), fwrite(), fprint(), or similar command, failed.

CAN'T READ

A read(), fgets(), or similar command failed.

CAN'T CREATE

A creat() call failed.

CAN'T ALLOCATE

A dynamic allocation failed.

CAN'T LOCK

An attempt to make a LCK (lock) file failed. In some situations, this error is fatal.

CAN'T STAT

A stat() call failed.

CAN'T CHMOD

A chmod() call failed.

CAN'T LINK

A link() call failed.

CAN'T CHDIR

A chdir() call failed.

CAN'T UNLINK

An unlink() call failed.

WRONG ROLE

This is an internal logic problem.

CAN'T MOVE TO CORRUPTDIR

An attempt to move some bad C. or X. files to the /var/spool/uucp/.Corrupt directory failed. The directory is probably missing or has wrong modes or owner.

CAN'T CLOSE

A close() or fclose() call failed.

FILE EXISTS

The creation of a C. or D. file is attempted, but the file exists. This error occurs when a problem arises with the sequence file access, which usually indicates a software error.

NO uucp SERVICE NUMBER

A TCP/IP call is attempted, but no entry is in /etc/services for UUCP.

BAD UID

The user ID is not in the password database. Check name service configuration.

BAD LOGIN_UID

Same as previous description.

BAD LINE

A bad line is in the Devices file. Not enough arguments on one or more lines.

SYSLST OVERFLOW

An internal table in gename.c overflowed. A single job attempted to talk to more than 30 systems.

TOO MANY SAVED C FILES

Same as previous description.

RETURN FROM fixline ioctl

An ioctl(2), which should never fail, failed. A system driver problem has occurred.

BAD SPEED

A bad line speed appears in the Devices or Systems file (Class or Speed field).

BAD OPTION

A bad line or option is in the Permissions file. This error must be fixed immediately.

PKCGET READ

The remote machine probably hung up. No action is needed.

PKXSTART

The remote machine aborted in a nonrecoverable way. This error can usually be ignored.

TOO MANY LOCKS

An internal problem has occurred. Contact your system vendor.

XMV ERROR

A problem with some file or directory has occurred. The spool directory is the probable cause, as the modes of the destinations were supposed to be checked before this process was attempted.

CAN'T FORK

An attempt to make a fork and exec failed. The current job should not be lost but will be attempted later (uuxqt). No action is needed.