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 IEEE Std 1003.1-2001.
32 Typical implementations of this utility require a communications line
34 configured to use the Base Definitions volume of IEEE Std 1003.1-2001,
35 Chapter 11, General Terminal Interface, but other communications means
36 may be used. On systems where there are no available communications
37 means (either temporarily or permanently), this utility shall write an
38 error message describing the problem and exit with a non-zero exit sta‐
39 tus.
40
42 The uucp utility shall conform to the Base Definitions volume of
43 IEEE Std 1003.1-2001, 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 trans‐
51 fer.
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 job
58 identification can be used by uustat to obtain the status or
59 terminate a job.
60 -m Send mail to the requester when the copy is completed.
62 -n user
64 Notify user on the remote system that a file was sent.
65 -r Do not start the file transfer; just queue the job.
67
70 The following operands shall be supported:
71 destination-file, source-file
73 A pathname of a file to be copied to, or from, respectively.
75 Either name can be a pathname on the local machine, or can have
76 the form:
77 system-name!pathname
80 where system-name is taken from a list of system names that uucp knows
82 about. The destination system-name can also be a list of names such as:
83 system-name!system-name!...!system-name!pathname
86 in which case, an attempt is made to send the file via the specified
88 route to the destination. Care should be taken to ensure that interme‐
89 diate nodes in the route are willing to forward information.
90 The shell pattern matching notation characters '?', '*', and "[...]"
92 appearing in pathname shall be expanded on the appropriate system.
93 Pathnames can be one of:
95 1. An absolute pathname.
97 2. A pathname preceded by ~ user where user is a login name on
99 the specified system and is replaced by that user's login
100 directory. Note that if an invalid login is specified, the
101 default is to the public directory (called PUBDIR; the
102 actual location of PUBDIR is implementation-defined).
103 3. A pathname preceded by ~/ destination where destination is
105 appended to PUBDIR.
106 Note:
108 This destination is treated as a filename unless more
109 than one file is being transferred by this request or the
110 destination is already a directory. To ensure that it is
111 a directory, follow the destination with a '/' . For
112 example, ~/dan/ as the destination makes the directory
113 PUBDIR/dan if it does not exist and puts the requested
114 files in that directory.
115 4. Anything else shall be prefixed by the current directory.
118 If the result is an erroneous pathname for the remote system, the copy
120 shall fail. If the destination-file is a directory, the last part of
121 the source-file name shall be used.
122 The read, write, and execute permissions given by uucp are implementa‐
124 tion-defined.
125
128 Not used.
129
131 The files to be copied are regular files.
132
134 The following environment variables shall affect the execution of uucp:
135 LANG Provide a default value for the internationalization variables
137 that are unset or null. (See the Base Definitions volume of
138 IEEE Std 1003.1-2001, Section 8.2, Internationalization Vari‐
139 ables for the precedence of internationalization variables used
140 to determine the values of locale categories.)
141 LC_ALL If set to a non-empty string value, override the values of all
143 the other internationalization variables.
144 LC_COLLATE
146 Determine the locale for the behavior of ranges, equivalence
148 classes, and multi-character collating elements within bracketed
149 filename patterns.
150 LC_CTYPE
152 Determine the locale for the interpretation of sequences of
153 bytes of text data as characters (for example, single-byte as
154 opposed to multi-byte characters in arguments and input files)
155 and the behavior of character classes within bracketed filename
156 patterns (for example, "'[[:lower:]]*'" ).
157 LC_MESSAGES
159 Determine the locale that should be used to affect the format
160 and contents of diagnostic messages written to standard error,
161 and informative messages written to standard output.
162 NLSPATH
164 Determine the location of message catalogs for the processing of
165 LC_MESSAGES .
166
169 Default.
170
172 Not used.
173
175 The standard error shall be used only for diagnostic messages.
176
178 The output files (which may be on other systems) are copies of the
179 input files.
180 If -m is used, mail files are modified.
182
184 None.
185
187 The following exit values shall be returned:
188 0 Successful completion.
190 >0 An error occurred.
192
195 Default.
196 The following sections are informative.
198
200 The domain of remotely accessible files can (and for obvious security
201 reasons usually should) be severely restricted.
202 Note that the '!' character in addresses has to be escaped when using
204 csh as a command interpreter because of its history substitution syn‐
205 tax. For ksh and sh the escape is not necessary, but may be used.
206 As noted above, shell metacharacters appearing in pathnames are
208 expanded on the appropriate system. On an internationalized system,
209 this is done under the control of local settings of LC_COLLATE and
210 LC_CTYPE. Thus, care should be taken when using bracketed filename
211 patterns, as collation and typing rules may vary from one system to
212 another. Also be aware that certain types of expression (that is,
213 equivalence classes, character classes, and collating symbols) need not
214 be supported on non-internationalized systems.
215
217 None.
218
220 None.
221
223 None.
224
226 mailx, uuencode, uustat, uux
227
229 Portions of this text are reprinted and reproduced in electronic form
230 from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
231 -- Portable Operating System Interface (POSIX), The Open Group Base
232 Specifications Issue 6, Copyright (C) 2001-2003 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 .
238IEEE/The Open Group 2003 UUCP(1P)