1UUCP(1P) POSIX Programmer's Manual UUCP(1P)
2
6 This manual page is part of the POSIX Programmer's Manual. The Linux
7 implementation of this interface may differ (consult the corresponding
8 Linux manual page for details of Linux behavior), or the interface may
9 not be implemented on Linux.
10
13 uucp — system-to-system copy
14
16 uucp [−cCdfjmr] [−n user] source-file... destination-file
17
19 The uucp utility shall copy files named by the source-file argument to
20 the destination-file argument. The files named can be on local or
21 remote systems.
22 The uucp utility cannot guarantee support for all character encodings
24 in all circumstances. For example, transmission data may be restricted
25 to 7 bits by the underlying network, 8-bit data and filenames need not
26 be portable to non-internationalized systems, and so on. Under these
27 circumstances, it is recommended that only characters defined in the
28 ISO/IEC 646:1991 standard International Reference Version (equivalent
29 to ASCII) 7-bit range of characters be used, and that only characters
30 defined in the portable filename character set be used for naming
31 files. The protocol for transfer of files is unspecified by
32 POSIX.1‐2008.
33 Typical implementations of this utility require a communications line
35 configured to use the Base Definitions volume of POSIX.1‐2008, Chapter
36 11, General Terminal Interface, but other communications means may be
37 used. On systems where there are no available communications means
38 (either temporarily or permanently), this utility shall write an error
39 message describing the problem and exit with a non-zero exit status.
40
42 The uucp utility shall conform to the Base Definitions volume of
43 POSIX.1‐2008, Section 12.2, Utility Syntax Guidelines.
44 The following options shall be supported:
46 −c Do not copy local file to the spool directory for transfer to
48 the remote machine (default).
49 −C Force the copy of local files to the spool directory for
51 transfer.
52 −d Make all necessary directories for the file copy (default).
54 −f Do not make intermediate directories for the file copy.
56 −j Write the job identification string to standard output. This
58 job identification can be used by uustat to obtain the status
59 or terminate a job.
60 −m Send mail to the requester when the copy is completed.
62 −n user Notify user on the remote system that a file was sent.
64 −r Do not start the file transfer; just queue the job.
66
68 The following operands shall be supported:
69 destination-file, source-file
71 A pathname of a file to be copied to, or from, respectively.
72 Either name can be a pathname on the local machine, or can
73 have the form:
74 system-name!pathname
76 where system-name is taken from a list of system names that
78 uucp knows about. The destination system-name can also be a
79 list of names such as:
80 system-name!system-name!...!system-name!pathname
82 in which case, an attempt is made to send the file via the
84 specified route to the destination. Care should be taken to
85 ensure that intermediate nodes in the route are willing to
86 forward information.
87 The shell pattern matching notation characters '?', '*', and
89 "[...]" appearing in pathname shall be expanded on the appro‐
90 priate system.
91 Pathnames can be one of:
93 1. An absolute pathname.
95 2. A pathname preceded by ~user where user is a login name
97 on the specified system and is replaced by that user's
98 login directory. Note that if an invalid login is speci‐
99 fied, the default is to the public directory (called PUB‐
100 DIR; the actual location of PUBDIR is implementation-
101 defined).
102 3. A pathname preceded by ~/destination where destination is
104 appended to PUBDIR.
105 Note: This destination is treated as a filename
107 unless more than one file is being transferred
108 by this request or the destination is already a
109 directory. To ensure that it is a directory,
110 follow the destination with a '/'. For exam‐
111 ple, ~/dan/ as the destination makes the direc‐
112 tory PUBDIR/dan if it does not exist and puts
113 the requested files in that directory.
114 4. Anything else shall be prefixed by the current directory.
116 If the result is an erroneous pathname for the remote system,
118 the copy shall fail. If the destination-file is a directory,
119 the last part of the source-file name shall be used.
120 The read, write, and execute permissions given by uucp are
122 implementation-defined.
123
125 Not used.
126
128 The files to be copied are regular files.
129
131 The following environment variables shall affect the execution of uucp:
132 LANG Provide a default value for the internationalization vari‐
134 ables that are unset or null. (See the Base Definitions vol‐
135 ume of POSIX.1‐2008, Section 8.2, Internationalization Vari‐
136 ables for the precedence of internationalization variables
137 used to determine the values of locale categories.)
138 LC_ALL If set to a non-empty string value, override the values of
140 all the other internationalization variables.
141 LC_COLLATE
143 Determine the locale for the behavior of ranges, equivalence
144 classes, and multi-character collating elements within brack‐
145 eted filename patterns.
146 LC_CTYPE Determine the locale for the interpretation of sequences of
148 bytes of text data as characters (for example, single-byte as
149 opposed to multi-byte characters in arguments and input
150 files) and the behavior of character classes within bracketed
151 filename patterns (for example, "'[[:lower:]]*'").
152 LC_MESSAGES
154 Determine the locale that should be used to affect the format
155 and contents of diagnostic messages written to standard
156 error, and informative messages written to standard output.
157 NLSPATH Determine the location of message catalogs for the processing
159 of LC_MESSAGES.
160
162 Default.
163
165 Not used.
166
168 The standard error shall be used only for diagnostic messages.
169
171 The output files (which may be on other systems) are copies of the
172 input files.
173 If −m is used, mail files are modified.
175
177 None.
178
180 The following exit values shall be returned:
181 0 Successful completion.
183 >0 An error occurred.
185
187 Default.
188 The following sections are informative.
190
192 This utility is part of the UUCP Utilities option and need not be sup‐
193 ported by all implementations.
194 The domain of remotely accessible files can (and for obvious security
196 reasons usually should) be severely restricted.
197 Note that the '!' character in addresses has to be escaped when using
199 csh as a command interpreter because of its history substitution syn‐
200 tax. For ksh and sh the escape is not necessary, but may be used.
201 As noted above, shell metacharacters appearing in pathnames are
203 expanded on the appropriate system. On an internationalized system,
204 this is done under the control of local settings of LC_COLLATE and
205 LC_CTYPE. Thus, care should be taken when using bracketed filename
206 patterns, as collation and typing rules may vary from one system to
207 another. Also be aware that certain types of expression (that is,
208 equivalence classes, character classes, and collating symbols) need not
209 be supported on non-internationalized systems.
210
212 None.
213
215 None.
216
218 None.
219
221 mailx, uuencode, uustat, uux
222 The Base Definitions volume of POSIX.1‐2008, Chapter 8, Environment
224 Variables, Chapter 11, General Terminal Interface, Section 12.2, Util‐
225 ity Syntax Guidelines
226
228 Portions of this text are reprinted and reproduced in electronic form
229 from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
230 -- Portable Operating System Interface (POSIX), The Open Group Base
231 Specifications Issue 7, Copyright (C) 2013 by the Institute of Electri‐
232 cal and Electronics Engineers, Inc and The Open Group. (This is
233 POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
234 event of any discrepancy between this version and the original IEEE and
235 The Open Group Standard, the original IEEE and The Open Group Standard
236 is the referee document. The original Standard can be obtained online
237 at http://www.unix.org/online.html .
238 Any typographical or formatting errors that appear in this page are
240 most likely to have been introduced during the conversion of the source
241 files to man page format. To report such errors, see https://www.ker‐
242 nel.org/doc/man-pages/reporting_bugs.html .
243IEEE/The Open Group 2013 UUCP(1P)