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
12 uucp — system-to-system copy
13
15 uucp [-cCdfjmr] [-n user] source-file... destination-file
16
18 The uucp utility shall copy files named by the source-file argument to
19 the destination-file argument. The files named can be on local or
20 remote systems.
21 The uucp utility cannot guarantee support for all character encodings
23 in all circumstances. For example, transmission data may be restricted
24 to 7 bits by the underlying network, 8-bit data and filenames need not
25 be portable to non-internationalized systems, and so on. Under these
26 circumstances, it is recommended that only characters defined in the
27 ISO/IEC 646:1991 standard International Reference Version (equivalent
28 to ASCII) 7-bit range of characters be used, and that only characters
29 defined in the portable filename character set be used for naming
30 files. The protocol for transfer of files is unspecified by
31 POSIX.1‐2008.
32 Typical implementations of this utility require a communications line
34 configured to use the Base Definitions volume of POSIX.1‐2017, Chapter
35 11, General Terminal Interface, but other communications means may be
36 used. On systems where there are no available communications means
37 (either temporarily or permanently), this utility shall write an error
38 message describing the problem and exit with a non-zero exit status.
39
41 The uucp utility shall conform to the Base Definitions volume of
42 POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
43 The following options shall be supported:
45 -c Do not copy local file to the spool directory for transfer to
47 the remote machine (default).
48 -C Force the copy of local files to the spool directory for
50 transfer.
51 -d Make all necessary directories for the file copy (default).
53 -f Do not make intermediate directories for the file copy.
55 -j Write the job identification string to standard output. This
57 job identification can be used by uustat to obtain the status
58 or terminate a job.
59 -m Send mail to the requester when the copy is completed.
61 -n user Notify user on the remote system that a file was sent.
63 -r Do not start the file transfer; just queue the job.
65
67 The following operands shall be supported:
68 destination-file, source-file
70 A pathname of a file to be copied to, or from, respectively.
71 Either name can be a pathname on the local machine, or can
72 have the form:
73 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
83 in which case, an attempt is made to send the file via the
85 specified route to the destination. Care should be taken to
86 ensure that intermediate nodes in the route are willing to
87 forward information.
88 The shell pattern matching notation characters '?', '*', and
90 "[...]" appearing in pathname shall be expanded on the appro‐
91 priate system.
92 Pathnames can be one of:
94 1. An absolute pathname.
96 2. A pathname preceded by ~user where user is a login name
98 on the specified system and is replaced by that user's
99 login directory. Note that if an invalid login is speci‐
100 fied, the default is to the public directory (called PUB‐
101 DIR; the actual location of PUBDIR is implementation-
102 defined).
103 3. A pathname preceded by ~/destination where destination is
105 appended to PUBDIR.
106 Note: This destination is treated as a filename
108 unless more than one file is being transferred
109 by this request or the destination is already a
110 directory. To ensure that it is a directory,
111 follow the destination with a '/'. For exam‐
112 ple, ~/dan/ as the destination makes the direc‐
113 tory PUBDIR/dan if it does not exist and puts
114 the requested files in that directory.
115 4. Anything else shall be prefixed by the current directory.
117 If the result is an erroneous pathname for the remote system,
119 the copy shall fail. If the destination-file is a directory,
120 the last part of the source-file name shall be used.
121 The read, write, and execute permissions given by uucp are
123 implementation-defined.
124
126 Not used.
127
129 The files to be copied are regular files.
130
132 The following environment variables shall affect the execution of uucp:
133 LANG Provide a default value for the internationalization vari‐
135 ables that are unset or null. (See the Base Definitions vol‐
136 ume of POSIX.1‐2017, Section 8.2, Internationalization Vari‐
137 ables for the precedence of internationalization variables
138 used to determine the values of locale categories.)
139 LC_ALL If set to a non-empty string value, override the values of
141 all the other internationalization variables.
142 LC_COLLATE
144 Determine the locale for the behavior of ranges, equivalence
145 classes, and multi-character collating elements within brack‐
146 eted filename patterns.
147 LC_CTYPE Determine the locale for the interpretation of sequences of
149 bytes of text data as characters (for example, single-byte as
150 opposed to multi-byte characters in arguments and input
151 files) and the behavior of character classes within bracketed
152 filename patterns (for example, "'[[:lower:]]*'").
153 LC_MESSAGES
155 Determine the locale that should be used to affect the format
156 and contents of diagnostic messages written to standard
157 error, and informative messages written to standard output.
158 NLSPATH Determine the location of message catalogs for the processing
160 of LC_MESSAGES.
161
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
188 Default.
189 The following sections are informative.
191
193 This utility is part of the UUCP Utilities option and need not be sup‐
194 ported by all implementations.
195 The domain of remotely accessible files can (and for obvious security
197 reasons usually should) be severely restricted.
198 Note that the '!' character in addresses has to be escaped when using
200 csh as a command interpreter because of its history substitution syn‐
201 tax. For ksh and sh the escape is not necessary, but may be used.
202 As noted above, shell metacharacters appearing in pathnames are
204 expanded on the appropriate system. On an internationalized system,
205 this is done under the control of local settings of LC_COLLATE and
206 LC_CTYPE. Thus, care should be taken when using bracketed filename
207 patterns, as collation and typing rules may vary from one system to
208 another. Also be aware that certain types of expression (that is,
209 equivalence classes, character classes, and collating symbols) need not
210 be supported on non-internationalized systems.
211
213 None.
214
216 None.
217
219 None.
220
222 mailx, uuencode, uustat, uux
223 The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment
225 Variables, Chapter 11, General Terminal Interface, Section 12.2, Util‐
226 ity Syntax Guidelines
227
229 Portions of this text are reprinted and reproduced in electronic form
230 from IEEE Std 1003.1-2017, Standard for Information Technology -- Por‐
231 table Operating System Interface (POSIX), The Open Group Base Specifi‐
232 cations Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of
233 Electrical and Electronics Engineers, Inc and The Open Group. 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.opengroup.org/unix/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 2017 UUCP(1P)