BSD 4_3_Tahoe development
[unix-history] / usr / man / cat1 / uusend.0
UUSEND(1C) UNIX Programmer's Manual UUSEND(1C)
N\bNA\bAM\bME\bE
uusend - send a file to a remote host
S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
u\buu\bus\bse\ben\bnd\bd [ -\b-m\bm mode ] sourcefile sys1!sys2!..!remotefile
D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
_\bU_\bu_\bs_\be_\bn_\bd sends a file to a given location on a remote system.
The system need not be directly connected to the local sys-
tem, but a chain of _\bu_\bu_\bc_\bp(1) links needs to connect the two
systems.
If the -\b-m\bm option is specified, the mode of the file on the
remote end will be taken from the octal number given. Oth-
erwise, 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 _\bu_\bu_\bs_\be_\bn_\bd.
The remotefile can include the ~userid syntax.
D\bDI\bIA\bAG\bGN\bNO\bOS\bST\bTI\bIC\bCS\bS
If anything goes wrong any further away than the first sys-
tem down the line, you will never hear about it.
S\bSE\bEE\bE A\bAL\bLS\bSO\bO
uux(1), uucp(1), uuencode(1)
B\bBU\bUG\bGS\bS
This command should not exist, since _\bu_\bu_\bc_\bp should handle it.
All systems along the line must have the _\bu_\bu_\bs_\be_\bn_\bd command
available and allow remote execution of it.
Some uucp systems have a bug where binary files cannot be
the input to a _\bu_\bu_\bx command. If this bug exists in any sys-
tem along the line, the file will show up severly munged.
Printed 7/9/88 April 24, 1986 1