uucp, uulog, uuname --
UNIX-to-UNIX system copy
[ -c | -C ] [ -d | -f ]
[ -jmr ] [ -g grade ]
[ -n user ] [ -s file ]
[ -x debug_level ] source-file ...
uulog [ -s system ] [ -x ]
uulog -f system [ -number ]
[ -x ]
uuname [ -l ] [ -c ]
uucp copies files named by the source-file
arguments to the destination-file argument. A filename may
be a pathname on your machine, or may have the form:
where system-name is taken from a list of system names
that uucp knows about. The system-name may also
be a list of names such as the following:
system-name!system-name! ... !system-name!pathname
In this case, an attempt is made to send the file via the specified
route, to the destination. See ``Limitations'' below for
restrictions. Care should be taken to ensure that intermediate nodes
in the route are willing to forward information.
The shell metacharacters ``?'', ``'' and [ ... ]
appearing in pathname will be expanded on the appropriate
Pathnames may be one of:
If the result is an erroneous pathname for the remote system, the
copy will fail. If the destination-file is a directory,
the last part of the source-file name is used.
A full pathname.
A pathname preceded by ~user where user is a
login name on the specified system and is replaced by that user's
A pathname preceded by ~/destination where
destination is appended to
/usr/spool/uucppublic; this destination will be treated as
a filename unless more than one file is being transferred by this
request or the destination is already a directory. To ensure that
destination is a directory, follow the destination with a
``/''. For example, ~/dan/ as the destination will
make the directory /usr/spool/uucppublic/dan if it does
not exist and put the requested file(s) in that directory.
Anything else, which gets prefixed by the current directory.
If a simple ~user destination is inaccessible to
uucp, data is copied to a spool directory and the user is
uucp preserves execute permissions across the transmission
and gives 0666 read and write permissions (see
The following options are interpreted by uucp:
uulog writes the status of uucp and
transactions to the standard output. (It queries the transaction log
files /usr/spool/uucp/.Log/uucico/system, or
By default, information is written about all known systems.
Do not copy local file to the spool directory for transfer to the
remote machine (default).
Force the copy of local files to the spool directory for transfer.
Make all necessary directories for the file copy (default).
Do not make intermediate directories for the file copy.
grade is a single letter/number; lower ASCII
sequence characters will cause the job to be transmitted earlier
during a particular conversation.
Print the job identification ASCII string on standard
output. This job identification can be used by uustat to
obtain the status or terminate a job.
Send mail to the requester when the copy is completed.
The -m option will only work when sending files or
receiving a single file. Receiving multiple files specified by
special shell characters ``?'', ``*'', [ ... ] will
not activate the -m option.
Notify user on the remote system that a file was sent.
Do not start the file transfer, just queue the job.
Report status of the transfer to file. Note that the
file must be a full pathname.
Produce debugging output on standard output. The
debug_level is a number between 0 and 9; higher numbers
give more detailed information.
uulog has the following options:
uuname lists the names of systems known to
uucp. It takes the following options:
Print information about file transfer operations for
Continuously monitors the file transfer log for system and
displays the output using tail -f. (You must press
DELETE or BREAK to exit.)
Indicates that tail should show number lines at
a time. Used with the -f option.
Look in the uuxqt log file for the given system, instead
of the uucico log file (the default).
Returns the names of systems known to cu instead of
uucp. (The two lists are the same, unless your machine is
using different Systems files for cu and
Returns the local system name.
The domain of remotely accessible files can (and for obvious
security reasons, usually should) be severely restricted. You may be
unable to fetch files by pathname; ask a responsible person on the
remote system to send them to you. For the same reasons, you may not
be able to send files to arbitrary pathnames. As distributed, the
remotely accessible files are those whose names begin
/usr/spool/uucppublic (equivalent to ~/).
All files received by uucp will be owned by uucp.
Protected files and files that are in protected directories that are
owned by the requester can be sent by uucp. However, if
the requester is root, and the directory is not searchable
by ``other'' or the file is not readable by ``other'', the request
The forwarding of files through other systems may not be compatible
with older (non-HDB) versions of uucp. If
forwarding is used, all systems in the route must have the same
version of uucp.
public directory for receiving and sending
other data and program files
uucp, uulog, and uuname are conformant
ISO/IEC DIS 99452:1992, Information technology Portable Operating System Interface (POSIX) Part 2: Shell and Utilities (IEEE Std 1003.21992);
AT&T SVID Issue 2;
X/Open CAE Specification, Commands and Utilities, Issue 4, 1992.
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 03 June 2005