1UUCP(P) POSIX Programmer's Manual UUCP(P)
2
6 uucp - system-to-system copy
7
9 uucp [-cCdfjmr][-n user] source-file... destination-file
10
12 The uucp utility shall copy files named by the source-file argument to
13 the destination-file argument. The files named can be on local or
14 remote systems.
15 The uucp utility cannot guarantee support for all character encodings
17 in all circumstances. For example, transmission data may be restricted
18 to 7 bits by the underlying network, 8-bit data and filenames need not
19 be portable to non-internationalized systems, and so on. Under these
20 circumstances, it is recommended that only characters defined in the
21 ISO/IEC 646:1991 standard International Reference Version (equivalent
22 to ASCII) 7-bit range of characters be used, and that only characters
23 defined in the portable filename character set be used for naming
24 files. The protocol for transfer of files is unspecified by
25 IEEE Std 1003.1-2001.
26 Typical implementations of this utility require a communications line
28 configured to use the Base Definitions volume of IEEE Std 1003.1-2001,
29 Chapter 11, General Terminal Interface, but other communications means
30 may be used. On systems where there are no available communications
31 means (either temporarily or permanently), this utility shall write an
32 error message describing the problem and exit with a non-zero exit sta‐
33 tus.
34
36 The uucp utility shall conform to the Base Definitions volume of
37 IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
38 The following options shall be supported:
40 -c Do not copy local file to the spool directory for transfer to
42 the remote machine (default).
43 -C Force the copy of local files to the spool directory for trans‐
45 fer.
46 -d Make all necessary directories for the file copy (default).
48 -f Do not make intermediate directories for the file copy.
50 -j Write the job identification string to standard output. This job
52 identification can be used by uustat to obtain the status or
53 terminate a job.
54 -m Send mail to the requester when the copy is completed.
56 -n user
58 Notify user on the remote system that a file was sent.
59 -r Do not start the file transfer; just queue the job.
61
64 The following operands shall be supported:
65 destination-file, source-file
67 A pathname of a file to be copied to, or from, respectively.
69 Either name can be a pathname on the local machine, or can have
70 the form:
71 system-name!pathname
74 where system-name is taken from a list of system names that uucp knows
76 about. The destination system-name can also be a list of names such as:
77 system-name!system-name!...!system-name!pathname
80 in which case, an attempt is made to send the file via the specified
82 route to the destination. Care should be taken to ensure that interme‐
83 diate nodes in the route are willing to forward information.
84 The shell pattern matching notation characters '?' , '*' , and "[...]"
86 appearing in pathname shall be expanded on the appropriate system.
87 Pathnames can be one of:
89 1. An absolute pathname.
91 2. A pathname preceded by ~ user where user is a login name on
93 the specified system and is replaced by that user's login
94 directory. Note that if an invalid login is specified, the
95 default is to the public directory (called PUBDIR; the
96 actual location of PUBDIR is implementation-defined).
97 3. A pathname preceded by ~/ destination where destination is
99 appended to PUBDIR.
100 Note:
102 This destination is treated as a filename unless more
103 than one file is being transferred by this request or the
104 destination is already a directory. To ensure that it is
105 a directory, follow the destination with a '/' . For
106 example, ~/dan/ as the destination makes the directory
107 PUBDIR/dan if it does not exist and puts the requested
108 files in that directory.
109 4. Anything else shall be prefixed by the current directory.
112 If the result is an erroneous pathname for the remote system, the copy
114 shall fail. If the destination-file is a directory, the last part of
115 the source-file name shall be used.
116 The read, write, and execute permissions given by uucp are implementa‐
118 tion-defined.
119
122 Not used.
123
125 The files to be copied are regular files.
126
128 The following environment variables shall affect the execution of uucp:
129 LANG Provide a default value for the internationalization variables
131 that are unset or null. (See the Base Definitions volume of
132 IEEE Std 1003.1-2001, Section 8.2, Internationalization Vari‐
133 ables for the precedence of internationalization variables used
134 to determine the values of locale categories.)
135 LC_ALL If set to a non-empty string value, override the values of all
137 the other internationalization variables.
138 LC_COLLATE
140 Determine the locale for the behavior of ranges, equivalence
142 classes, and multi-character collating elements within bracketed
143 filename patterns.
144 LC_CTYPE
146 Determine the locale for the interpretation of sequences of
147 bytes of text data as characters (for example, single-byte as
148 opposed to multi-byte characters in arguments and input files)
149 and the behavior of character classes within bracketed filename
150 patterns (for example, "'[[:lower:]]*'" ).
151 LC_MESSAGES
153 Determine the locale that should be used to affect the format
154 and contents of diagnostic messages written to standard error,
155 and informative messages written to standard output.
156 NLSPATH
158 Determine the location of message catalogs for the processing of
159 LC_MESSAGES .
160
163 Default.
164
166 Not used.
167
169 The standard error shall be used only for diagnostic messages.
170
172 The output files (which may be on other systems) are copies of the
173 input files.
174 If -m is used, mail files are modified.
176
178 None.
179
181 The following exit values shall be returned:
182 0 Successful completion.
184 >0 An error occurred.
186
189 Default.
190 The following sections are informative.
192
194 The domain of remotely accessible files can (and for obvious security
195 reasons usually should) be severely restricted.
196 Note that the '!' character in addresses has to be escaped when using
198 csh as a command interpreter because of its history substitution syn‐
199 tax. For ksh and sh the escape is not necessary, but may be used.
200 As noted above, shell metacharacters appearing in pathnames are
202 expanded on the appropriate system. On an internationalized system,
203 this is done under the control of local settings of LC_COLLATE and
204 LC_CTYPE . Thus, care should be taken when using bracketed filename
205 patterns, as collation and typing rules may vary from one system to
206 another. Also be aware that certain types of expression (that is,
207 equivalence classes, character classes, and collating symbols) need not
208 be supported on non-internationalized systems.
209
211 None.
212
214 None.
215
217 None.
218
220 mailx , uuencode , uustat , uux
221
223 Portions of this text are reprinted and reproduced in electronic form
224 from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
225 -- Portable Operating System Interface (POSIX), The Open Group Base
226 Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
227 Electrical and Electronics Engineers, Inc and The Open Group. In the
228 event of any discrepancy between this version and the original IEEE and
229 The Open Group Standard, the original IEEE and The Open Group Standard
230 is the referee document. The original Standard can be obtained online
231 at http://www.opengroup.org/unix/online.html .
232IEEE/The Open Group 2003 UUCP(P)