solaris - uucp (1)
NAME
uucp, uulog, uuname - UNIX-to-UNIX system copy
SYNOPSIS
uucp [ -c | -C ] [ -d | -f ] [ -ggrade ] [ -jmr ]
[ -nuser ] [ -sfile ] [ -xdebug_level ]
source-file destination-file
uulog [ -ssys ] [ -fsystem ] [ -x ] [ -number ] system
uuname [ -c|-l ]
AVAILABILITY
SUNWbnuu
DESCRIPTION
uucp
uucp copies files named by the source-file arguments to the
destination-file argument.
uulog
uulog queries a log file of uucp or uuxqt transactions in
file /var/uucp/.Log/uucico/system or
/var/uucp/.Log/uuxqt/system.
uuname
uuname lists the names of systems known to uucp.
OPTIONS
uucp
The following options are supported by uucp:
-c Do not copy local file to the spool direc-
tory for transfer to the remote machine
(default).
-C Force the copy of local files to the spool
directory for transfer.
-d Make all necessary directories for the file
copy (default).
-f Do not make intermediate directories for the
file copy.
-ggrade grade can be either a single letter, number,
or a string of alphanumeric characters defin-
ing a service grade. The uuglist command can
determine whether it is appropriate to use
the single letter, number, or a string of
alphanumeric characters as a service grade.
The output from the uuglist command will be a
list of service grades that are available, or
a message that says to use a single letter or
number as a grade of service.
-j Print the uucp job identification string on
standard output. This job identification can
be used by uustat to obtain the status of a
uucp job or to terminate a uucp job. The
uucp job is valid as long as the job remains
queued on the local system.
-m Send mail to the requester when the copy is
complete.
-nuser Notify user on the remote system that a file
was sent.
-r Do not start the file transfer, just queue
the job.
-sfile Report status of the transfer to file. This
option is accepted for compatibility, but it
is ignored because it is insecure.
-xdebug_level Produce debugging output on standard output.
debug_level is a number between 0 and 9; as
it increases to 9, more detailed debugging
information is given. This option may not be
available on all systems.
uulog
The following options cause uulog to print logging informa-
tion:
-ssys Print information about file transfer work
involving system sys.
-fsystem Do a "tail -f" of the file transfer log for
system. (You must hit BREAK to exit this
function.)
Other options used in conjunction with the above options
are:
-x Look in the uuxqt log file for the given
system.
-number Execute a tail command of number lines.
uuname
The following options are supported by uuname:
-c Display the names of systems known to cu.
The two lists are the same, unless your
machine is using different Systems files for
cu and uucp. See the Sysfiles file.
-l Display the local system name.
OPERANDS
The source file name may be a path name on your machine, or
may have the form:
system-name!pathname
where system-name is taken from a list of system names that
uucp knows about. source_file is restricted to no more than
one system-name. The destination system-name may also
include a list of system names such as
system-name!system-name!...!system-name!pathname
In this case, an attempt is made to send the file, using the
specified route, to the destination. Care should be taken
to ensure that intermediate nodes in the route are willing
to forward information (see NOTES below for restrictions).
For C-Shell users, the ``!'' character must be surrounded by
single quotes ('), or preceded by a backslash (\).
The shell metacharacters ?, * and [...] appearing in path-
name will be expanded on the appropriate system.
Pathnames may be one of the following:
(1) An absolute pathname.
(2) A pathname preceded by ~user where user is a login
name on the specified system and is replaced by
that user's login directory.
(3) A pathname preceded by ~/destination where desti-
nation is appended to /var/spool/uucppublic.
(Note: 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 the destina-
tion is a directory, follow it with a '/'. For
example ~/dan/ as the destination will make the
directory /var/spool/uucppublic/dan if it does not
exist and put the requested file(s) in that
directory).
Anything else is prefixed by the current directory.
If the result is an erroneous path name for the remote sys-
tem, the copy will fail. If the destination-file is a
directory, the last part of the source-file name is used.
Invoking uucp with shell wildcard characters as the remote
source-file invokes the uux(1C) command to execute the uucp
command on the remote machine. The remote uucp command
spools the files on the remote machine. After the first ses-
sion terminates, if the remote machine is configured to
transfer the spooled files to the local machine, the remote
machine will initiate a call and send the files; otherwise,
the user must "call" the remote machine to transfer the
files from the spool directory to the local machine. This
call can be done manually using Uutry(1M), or as a side
effect of another uux(1C) or uucp call.
Note that the local machine must have permission to execute
the uucp command on the remote machine in order for the
remote machine to send the spooled files.
uucp removes execute permissions across the transmission and
gives 0666 read and write permissions (see chmod(2)).
ENVIRONMENT
See environ(5) for descriptions of the following environment
variables that affect the execution of uucp: LC_COLLATE,
LC_CTYPE, LC_MESSAGES, LC_TIME, TZ, and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 Successful completion.
>0 An error occurred.
FILES
/etc/uucp/* other data files
/var/spool/uucp spool directories
/usr/lib/uucp/* other program files
/var/spool/uucppublic/* public directory for receiving and
sending
SEE ALSO
mail(1), uuglist(1C), uustat(1C), uux(1C), Uutry(1M),
uuxqt(1M), chmod(2)
NOTES
For security reasons, the domain of remotely accessible
files may be severely restricted. You will probably not be
able to access files by path name; ask a responsible person
on the remote system to send them to you. For the same rea-
sons you will probably not be able to send files to arbi-
trary path names. As distributed, the remotely accessible
files are those whose names begin /var/spool/uucppublic
(equivalent to ~/).
All files received by uucp will be owned by uucp.
The -m option will only work when sending files or receiving
a single file. Receiving multiple files specified by spe-
cial shell characters ?, &, and [...] will not activate the
-m option.
The forwarding of files through other systems may not be
compatible with the previous version of uucp. If forwarding
is used, all systems in the route must have compatible ver-
sions of uucp.
Protected files and files that are in protected directories
that are owned by the requester can be sent by uucp. How-
ever, if the requester is root, and the directory is not
searchable by "other" or the file is not readable by
"other", the request will fail.
Strings that are passed to remote systems may not be
evaluated in the same locale as the one in use by the pro-
cess that invoked uucp on the local system.
Configuration files must be treated as C (or POSIX) locale
text files.