|HP-UX Reference > U
HP-UX 11i Version 3: February 2007
uucp, uulog, uuname, uutry — UNIX system to UNIX system copy
uucp [options] source_files destination_file
uulog -f system [-x] [- number]
uulog [-s system]... [-x] [- number]
uutry -r1 -s system [-x debug_level]
uucp copies files named by the source_files argument to the destination identified by the destination_file argument. When copying files to or from a remote system, source_files and destination_file can be a path name on the local system, or have the form:
where system_name is the name of a remote system in a list of system names known to uucp. When copying files to (but not from) a remote system, system_name can also be a chained list of remote system names such as:
in which case an attempt is made to send the file, via the specified route, to the destination. Care should be taken to ensure that intermediate nodes in the route are configured to forward information (see WARNINGS for restrictions).
The shell metacharacters ?, *, and [...] appearing in path_name are expanded on the appropriate system.
path_name can be one of:
If an erroneous path name is specified for the remote system, the copy fails. If destination_file is a directory, the file name part of the source_file argument is used.
uucp preserves execute permissions across the transmission and sets read and write permissions to 0666 (see chmod(2) and Access Control Lists below).
uucp recognizes the following options:
uulog queries a log file of uucp transactions in a file /var/uucp/.Log/uucico/ system.
The following options cause uulog to print logging information:
Other options used in conjunction with the -s and -f options above are:
uuname lists the uucp names of known systems. uuname -l returns the local system's default name.
uutry tests for the successful login to the remote system. This is executed for checking communication channel.
When started by a local program, uutry is considered the MASTER and attempts a connection to a remote system. If uutry is started by a remote system, it is considered to be in SLAVE mode.
Access Control Lists (ACLs)
A file's optional ACL entries are not preserved across uucp transmission. Instead, new files have a summary of the access modes (as returned in st_mode by stat(); see stat(2)).
LC_TIME determines the format and contents of date and time strings displayed by uucp and uulog commands.
LANG determines the language in which messages are displayed by uucp and uuname commands.
If LC_TIME is not specified in the environment or is set to the empty string, the value of LANG is used as a default for each unspecified or empty variable. If LANG is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of LANG. If any internationalization variable contains an invalid setting, uucp, uulog, and uuname behave as if all internationalization variables are set to "C". See environ(5).
The domain of remotely accessible files can (and for obvious security reasons, usually should) be severely restricted. In most cases, you cannot fetch files by path name from a remote system. Ask a responsible person on the remote system to send them to you. For the same reasons, you probably cannot send files to arbitrary path names. As distributed, remotely accessible files are those whose names begin /var/spool/uucppublic (equivalent to ~/).
All files received by uucp are owned by uucp.
The -m option only works when sending files or when receiving a single file. Receiving multiple files specified by special shell characters ?, *, and [...] does not activate the -m option.
Protected files and files in protected directories 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 fails.
uutry should be executed only with a request file that exists in the directory /var/spool/uucp/system_name/.
Managing UUCP and Usenet, O'Reilly & Associates, Inc. USA.
Using UUCP and Usenet, O'Reilly & Associates, Inc. USA.