


      UUUUUUUUSSSSEEEENNNNDDDD((((1111))))                   ((((bbbbssssdddd 4444....2222))))                   UUUUUUUUSSSSEEEENNNNDDDD((((1111))))



      NNNNAAAAMMMMEEEE
           uusend - send a file to a remote host

      SSSSYYYYNNNNTTTTAAAAXXXX
           uuuuuuuusssseeeennnndddd [ ----mmmm mode ] sourcefile sys1!sys2!..!remotefile

      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
           _U_u_s_e_n_d sends a file to a given location on a remote system.
           The system need not be directly connected to the local
           system, but a chain of _u_u_c_p(1) links needs to connect the
           two systems.

           If the ----mmmm option is specified, the mode of the file on the
           remote end will be taken from the octal number given.
           Otherwise, the mode of the input file will be used.

           The sourcefile can be ``-'', meaning to use the standard
           input.  Both of these options are primarily intended for
           internal use of uusend.

           The remotefile can include the ~userid syntax defined in
           _u_u_c_p(_1).

      DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
           If anything goes wrong any further away than the first
           system down the line, you will never hear about it.

      SSSSEEEEEEEE AAAALLLLSSSSOOOO
           uux(1), uucp(1), uuencode(1)

      BBBBUUUUGGGGSSSS
           This command shouldn't exist, since _u_u_c_p should handle it.

           All systems along the line must have the _u_u_s_e_n_d command
           available and allow remote execution of it.

           Some uucp systems have a bug where binary files cannot be
           the input to a uux command.  If this bug exists in any
           system along the line, the file will show up severly munged.
















      Page 1                                                   (9010-E)



