1uucp(1C) Communication Commands uucp(1C)
2
6 uucp, uulog, uuname - UNIX-to-UNIX system copy
7
9 uucp [-c | -C] [-d | -f] [-ggrade] [-jmr] [-nuser] [-sfile]
10 [-xdebug_level] source-file destination-file
11 uulog [-ssys] [-fsystem] [-x] [-number] system
14 uuname [-c | -l]
17
20 uucp
21 The uucp utility copies files named by the source-file arguments to the
22 destination-file argument.
23 uulog
25 The uulog utility queries a log file of uucp or uuxqt transactions in
26 file /var/uucp/.Log/uucico/system or /var/uucp/.Log/uuxqt/system.
27 uuname
29 The uuname utility lists the names of systems known to uucp.
30
32 uucp
33 The following options are supported by uucp:
34 -c Does not copy local file to the spool directory for
36 transfer to the remote machine (default).
37 -C Forces the copy of local files to the spool directory
40 for transfer.
41 -d Makes all necessary directories for the file copy
44 (default).
45 -f Does not make intermediate directories for the file
48 copy.
49 -g grade grade can be either a single letter, number, or a
52 string of alphanumeric characters defining a service
53 grade. The uuglist command can determine whether it
54 is appropriate to use the single letter, number, or a
55 string of alphanumeric characters as a service grade.
56 The output from the uuglist command is a list of ser‐
57 vice grades that are available, or a message that
58 says to use a single letter or number as a grade of
59 service.
60 -j Prints the uucp job identification string on standard
63 output. This job identification can be used by uustat
64 to obtain the status of a uucp job or to terminate a
65 uucp job. The uucp job is valid as long as the job
66 remains queued on the local system.
67 -m Sends mail to the requester when the copy is com‐
70 plete.
71 -n user Notifies user on the remote system that a file was
74 sent.
75 When multiple -n options are passed in, uucp only
77 retains the value specified for the last -n option.
78 This is the only user notified.
79 -r Does not start the file transfer, just queue the job.
82 -s file Reports status of the transfer to file. This option
85 is accepted for compatibility, but it is ignored
86 because it is insecure.
87 -x debug_level Produce debugging output on standard output.
90 debug_level is a number between 0 and 9. As
91 debug_level increases to 9, more detailed debugging
92 information is given. This option may not be avail‐
93 able on all systems.
94 uulog
97 The following options cause uulog to print logging information:
98 -s sys Prints information about file transfer work involving sys‐
100 tem sys.
101 -f system Executes a tail -f command of the file transfer log for
104 system. You must press BREAK to exit this function.
105 Other options used in conjunction with the above options are:
109 -x Looks in the uuxqt log file for the given system.
111 -number Executes a tail command of number lines.
114 uuname
117 The following options are supported by uuname:
118 -c Displays the names of systems known to cu. The two lists are the
120 same, unless your machine is using different Systems files for cu
121 and uucp. See the Sysfiles file.
122 -l Displays the local system name.
125
128 The source file name may be a path name on your machine, or may have
129 the form:
130 system-name!pathname
132 where system-name is taken from a list of system names that uucp knows
137 about. source_file is restricted to no more than one system-name. The
138 destination system-name may also include a list of system names such as
139 system-name!system-name!...!system-name!pathname
141 In this case, an attempt is made to send the file, using the specified
146 route, to the destination. Care should be taken to ensure that interme‐
147 diate nodes in the route are willing to forward information. See NOTES
148 for restrictions.
149 For C-Shell users, the exclamation point (!) character must be sur‐
152 rounded by single quotes ('), or preceded by a backslash (\).
153 The shell metacharacters ?, * and [...] appearing in pathname are
156 expanded on the appropriate system.
157 Pathnames may be one of the following:
160 1. An absolute pathname.
162 2. A pathname preceded by ~user where user is a login name on
164 the specified system and is replaced by that user's login
165 directory.
166 3. A pathname preceded by ~/destination where destination is
168 appended to /var/spool/uucppublic. This destination is
169 treated as a filename unless more than one file is being
170 transferred by this request or the destination is already a
171 directory. To ensure that the destination is a directory,
172 follow it with a forward slash (/). For example, ~/dan/ as
173 the destination creates the directory /var/spool/uucppub‐
174 lic/dan if it does not exist and put the requested file(s)
175 in that directory.
176 Anything else is prefixed by the current directory.
179 If the result is an erroneous path name for the remote system, the copy
182 fails. If the destination-file is a directory, the last part of the
183 source-file name is used.
184 Invoking uucp with shell wildcard characters as the remote source-file
187 invokes the uux(1C) command to execute the uucp command on the remote
188 machine. The remote uucp command spools the files on the remote
189 machine. After the first session terminates, if the remote machine is
190 configured to transfer the spooled files to the local machine, the
191 remote machine initiates a call and send the files; otherwise, the user
192 must "call" the remote machine to transfer the files from the spool
193 directory to the local machine. This call can be done manually using
194 Uutry(1M), or as a side effect of another uux(1C) or uucp call.
195 Notice that the local machine must have permission to execute the uucp
198 command on the remote machine in order for the remote machine to send
199 the spooled files.
200 uucp removes execute permissions across the transmission and gives 0666
203 read and write permissions (see chmod(2)).
204
206 See environ(5) for descriptions of the following environment variables
207 that affect the execution of uucp: LANG, LC_ALL, LC_COLLATE, LC_CTYPE,
208 LC_MESSAGES, LC_TIME, NLSPATH, and TZ.
209
211 The following exit values are returned:
212 0 Successful completion.
214 >0 An error occurred.
217
220 /etc/uucp/* other data files
221 /var/spool/uucp spool directories
224 /usr/lib/uucp/* other program files
227 /var/spool/uucppublic/* public directory for receiving and sending
230
233 See attributes(5) for descriptions of the following attributes:
234 ┌─────────────────────────────┬─────────────────────────────┐
239 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
240 ├─────────────────────────────┼─────────────────────────────┤
241 │Availability │SUNWbnuu │
242 ├─────────────────────────────┼─────────────────────────────┤
243 │Interface Stability │Standard │
244 └─────────────────────────────┴─────────────────────────────┘
245
247 mail(1), uuglist(1C), uustat(1C), uux(1C), Uutry(1M), uuxqt(1M),
248 chmod(2), attributes(5), environ(5), standards(5)
249
251 For security reasons, the domain of remotely accessible files may be
252 severely restricted. You probably are not able to access files by path
253 name. Ask a responsible person on the remote system to send them to
254 you. For the same reasons you are probably not able to send files to
255 arbitrary path names. As distributed, the remotely accessible files are
256 those whose names begin /var/spool/uucppublic (equivalent to ~/).
257 All files received by uucp are owned by uucp.
260 The -m option only works when sending files or receiving a single file.
263 Receiving multiple files specified by special shell characters ?, &,
264 and [...] does not activate the -m option.
265 The forwarding of files through other systems may not be compatible
268 with the previous version of uucp. If forwarding is used, all systems
269 in the route must have compatible versions of uucp.
270 Protected files and files that are in protected directories that are
273 owned by the requester can be sent by uucp. However, if the requester
274 is root, and the directory is not searchable by "other" or the file is
275 not readable by "other", the request fails.
276 Strings that are passed to remote systems may not be evaluated in the
279 same locale as the one in use by the process that invoked uucp on the
280 local system.
281 Configuration files must be treated as C (or POSIX) locale text files.
284SunOS 5.11 9 Mar 2005 uucp(1C)