32v 1m uucp

From Computer History Wiki
Jump to: navigation, search

UUCP(1C) UNIX Programmer's Manual UUCP(1C)


    uucp, uulog - unix to unix copy


    uucp [ option ] ...  source-file ...  destination-file
    uulog [ option ] ...


    _U_u_c_p copies files named by the source-file arguments to the
    destination-file argument.  A file name may be a path name
    on your machine, or may have the form
    where `system-name' is taken from a list of system names
    which _u_u_c_p knows about.  Shell metacharacters ?*[] appearing
    in the pathname part will be expanded on the appropriate
    Pathnames may be one of
    (1)  a full pathname;
    (2)  a pathname preceded by ~_u_s_e_r; where _u_s_e_r is a userid on
         the specified system and is replaced by that user's
         login directory;
    (3)  anything else is prefixed by the current directory.
    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.
    _U_u_c_p preserves execute permissions across the transmission
    and gives 0666 read and write permissions (see _c_h_m_o_d(2)).
    The following options are interpreted by _u_u_c_p.
    -d   Make all necessary directories for the file copy.
    -c   Use the source file when copying out rather than copy-
         ing the file to the spool directory.
    -m   Send mail to the requester when the copy is complete.
    _U_u_l_o_g maintains a summary log of _u_u_c_p and _u_u_x(1) transac-
    tions in the file `/usr/spool/uucp/LOGFILE' by gathering
    information from partial log files named
    `/usr/spool/uucp/LOG.*.?'.  It removes the partial log
    The options cause _u_u_l_o_g to print logging information:
         Print information about work involving system _s_y_s.
         Print information about work done for the specified


    /usr/spool/uucp - spool directory
    /usr/lib/uucp/* - other data and program files


    uux(1), mail(1)
    D. A. Nowitz, _U_u_c_p _I_m_p_l_e_m_e_n_t_a_t_i_o_n _D_e_s_c_r_i_p_t_i_o_n


    The domain of remotely accessible files can (and for obvious
    security reasons, usually should) be severely restricted.
    You will very likely not be able to fetch files by pathname;
    ask a responsible person on the remote system to send them
    to you.  For the same reasons you will probably not be able
    to send files to arbitrary pathnames.


    All files received by _u_u_c_p will be owned by uucp.
    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.)