uucp - phpMan

UUCP(P) UUCP(P)

NAME
uucp - system-to-system copy

SYNOPSIS
uucp [-cCdfjmr][-n user] source-file... destination-file

DESCRIPTION
The uucp utility shall copy files named by the source-file argument to the destina-
tion-file argument. The files named can be on local or remote systems.

The uucp utility cannot guarantee support for all character encodings in all cir-
cumstances. For example, transmission data may be restricted to 7 bits by the
underlying network, 8-bit data and filenames need not be portable to non-interna-
tionalized systems, and so on. Under these circumstances, it is recommended that
only characters defined in the ISO/IEC 646:1991 standard International Reference
Version (equivalent to ASCII) 7-bit range of characters be used, and that only
characters defined in the portable filename character set be used for naming files.
The protocol for transfer of files is unspecified by IEEE Std 1003.1-2001.

Typical implementations of this utility require a communications line configured to
use the Base Definitions volume of IEEE Std 1003.1-2001, Chapter 11, General Termi-
nal Interface, but other communications means may be used. On systems where there
are no available communications means (either temporarily or permanently), this
utility shall write an error message describing the problem and exit with a non-
zero exit status.

OPTIONS
The uucp utility shall conform to the Base Definitions volume of
IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.

The following options shall be supported:

-c Do not copy local file to the spool directory 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.

-j Write the job identification string to standard output. This job identifica-
tion can be used by uustat to obtain the status or terminate a job.

-m Send mail to the requester when the copy is completed.

-n user
Notify user on the remote system that a file was sent.

-r Do not start the file transfer; just queue the job.

OPERANDS
The following operands shall be supported:

destination-file, source-file

A pathname of a file to be copied to, or from, respectively. Either name can
be a pathname on the local machine, or can have the form:

system-name!pathname

where system-name is taken from a list of system names that uucp knows about. The
destination system-name can also be a list of names such as:

system-name!system-name!...!system-name!pathname

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 willing to forward information.

The shell pattern matching notation characters â€â€™?â€â€™ , â€â€™*â€â€™ , and "[...]" appearing in
pathname shall be expanded on the appropriate system.

Pathnames can be one of:

1. An absolute pathname.

2. A pathname preceded by ~ user where user is a login name on the speci-
fied system and is replaced by that userâ€™s login directory. Note that if
an invalid login is specified, the default is to the public directory
(called PUBDIR; the actual location of PUBDIR is implementation-
defined).

3. A pathname preceded by ~/ destination where destination is appended to
PUBDIR.

Note:
This destination is 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 it is a directory, follow the destination
with a â€â€™/â€â€™ . For example, ~/dan/ as the destination makes the direc-
tory PUBDIR/dan if it does not exist and puts the requested files in
that directory.

4. Anything else shall be prefixed by the current directory.

If the result is an erroneous pathname for the remote system, the copy shall fail.
If the destination-file is a directory, the last part of the source-file name shall
be used.

The read, write, and execute permissions given by uucp are implementation-defined.

STDIN
Not used.

INPUT FILES
The files to be copied are regular files.

ENVIRONMENT VARIABLES
The following environment variables shall affect the execution of uucp:

LANG Provide a default value for the internationalization variables that are
unset or null. (See the Base Definitions volume of IEEE Std 1003.1-2001,
Section 8.2, Internationalization Variables for the precedence of interna-
tionalization variables used to determine the values of locale categories.)

LC_ALL If set to a non-empty string value, override the values of all the other
internationalization variables.

LC_COLLATE

Determine the locale for the behavior of ranges, equivalence classes, and
multi-character collating elements within bracketed filename patterns.

LC_CTYPE
Determine the locale for the interpretation of sequences of bytes of text
data as characters (for example, single-byte as opposed to multi-byte char-
acters in arguments and input files) and the behavior of character classes
within bracketed filename patterns (for example, "â€â€™[[:lower:]]*â€â€™" ).

LC_MESSAGES
Determine the locale that should be used to affect the format and contents
of diagnostic messages written to standard error, and informative messages
written to standard output.

NLSPATH
Determine the location of message catalogs for the processing of LC_MESSAGES
.

ASYNCHRONOUS EVENTS
Default.

STDOUT
Not used.

STDERR
The standard error shall be used only for diagnostic messages.

OUTPUT FILES
The output files (which may be on other systems) are copies of the input files.

If -m is used, mail files are modified.

EXTENDED DESCRIPTION
None.

EXIT STATUS
The following exit values shall be returned:

0 Successful completion.

>0 An error occurred.

CONSEQUENCES OF ERRORS
Default.

The following sections are informative.

APPLICATION USAGE
The domain of remotely accessible files can (and for obvious security reasons usu-
ally should) be severely restricted.

Note that the â€â€™!â€â€™ character in addresses has to be escaped when using csh as a com-
mand interpreter because of its history substitution syntax. For ksh and sh the
escape is not necessary, but may be used.

As noted above, shell metacharacters appearing in pathnames are expanded on the
appropriate system. On an internationalized system, this is done under the control
of local settings of LC_COLLATE and LC_CTYPE . Thus, care should be taken when
using bracketed filename patterns, as collation and typing rules may vary from one
system to another. Also be aware that certain types of expression (that is, equiva-
lence classes, character classes, and collating symbols) need not be supported on
non-internationalized systems.

EXAMPLES
None.

RATIONALE
None.

FUTURE DIRECTIONS
None.

SEE ALSO
mailx , uuencode , uustat , uux

COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std
1003.1, 2003 Edition, Standard for Information Technology -- Portable Operating
System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C)
2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The
Open Group. In the event of any discrepancy between this version and the original
IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is
the referee document. The original Standard can be obtained online at
http://www.opengroup.org/unix/online.html .

POSIX 2003 UUCP(P)

Generated by $Id: phpMan.php,v 4.55 2007/09/05 04:42:51 chedong Exp $ Author: Che Dong
On Apache/1.3.41 (Unix) PHP/5.2.5 mod_perl/1.30 mod_gzip/1.3.26.1a
Under GNU General Public License
2008-11-24 02:35 @38.103.63.58 CrawledBy CCBot/1.0 (+http://www.commoncrawl.org/bot.html)