The Regents of the University of California. All rights reserved.
%sccs.include.proprietary.roff%
@(#)uucp.1 8.1 (Berkeley) 06/06/93
where `system-name' is taken from a list of system names that uucp knows about. Shell metacharacters ?*[] appearing in the pathname part will be expanded on the appropriate system.
Pathnames may be one of:
If the result is an erroneous pathname for the remote system, the copy will fail. If the destination-file is a directory, the last part of the source-file name is used. If a simple ~user destination is inaccessible to uucp , data is copied to a spool directory and the user is notified by mail (1). ..
Uucp preserves execute permissions across the transmission and gives 0666 read and write permissions (see chmod (2)).
The following options are interpreted by uucp .
-a Avoid doing a getwd to find the current directory. (This is sometimes used for efficiency.)
-c Use the source file when copying out rather than copying the file to the spool directory. (This is the default.)
-C Copy the source file to the spool directory and transmit the copy.
-d Make all necessary directories for the file copy. (This is the default.)
-f Do not make intermediate directories for the file copy.
-g grade Grade is a single letter/number; lower ASCII sequence characters will cause a job to be transmitted earlier during a particular conversation. Default is `n'. By way of comparison, uux (1) defaults to `A'; mail is usually sent at `C'.
-m Send mail to the requester when the copy is complete.
-n user Notify user on remote system (i.e., send user mail) that a file was sent.
-r Do not start the transfer, just queue the job.
-s spool Use spool as the spool directory instead of the default.
-x debug Turn on the debugging at level debug.
/usr/lib/uucp/* - other data and program files
D. A. Nowitz and M. E. Lesk, "A Dial-Up Network of UNIX Systems" .
D. A. Nowitz, "Uucp Implementation Description" .
All files received by uucp will be owned by the uucp administrator (usually UID 5).
The -m option will only work sending files or receiving a single file. (Receiving multiple files specified by special shell characters ?*[] will not activate the -m option.)
At present uucp cannot copy to a system several "hops" away, that is, a command of the form
uucp myfile system1!system2!system3!yourfile
is not permitted. Use uusend (1) instead.
When invoking uucp from csh (1), the `!' character must be prefixed by the `\e' escape to inhibit csh 's history mechanism. (Quotes are not sufficient.)
Uucp refuses to copy a file that does not give read access to ``other''; that is, the file must have at least 0444 modes.