1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" %sccs.include.redist.roff% 5.\" 6.\" @(#)uusend.1 8.3 (Berkeley) 02/16/94 7.\" 8.Dd 9.Dt UUSEND 1 10.Os BSD 4 11.Sh NAME 12.Nm uusend 13.Nd send a file to a remote host 14.Sh SYNOPSIS 15.Nm uusend 16.Op Fl m Ar mode 17.Ar sourcefile 18.Ar sys1!sys2!..!remotefile 19.Sh DESCRIPTION 20.Nm Uusend 21sends a file to a given location on a remote system. 22The system need not be directly connected to the local 23system, but a chain of 24.Xr uucp 1 25links must to connect the two systems. 26.Pp 27Available option: 28.Bl -tag -width Fl 29.It Fl m Ar mode 30The mode of the file on the remote 31end is taken from the octal number given. 32Otherwise, the mode of the input file will be used. 33.El 34.Pp 35The sourcefile 36can be 37.Ql Fl , 38meaning to use the standard input. 39Both of these options are primarily intended for internal use of 40.Nm uusend . 41.Pp 42The remotefile can include the 43.Em ~userid 44syntax. 45.Sh DIAGNOSTICS 46If anything goes wrong any further away than the first system down 47the line, you will never hear about it. 48.Sh SEE ALSO 49.Xr uux 1 , 50.Xr uucp 1 , 51.Xr uuencode 1 52.Sh BUGS 53This command should not exist, since 54.Xr uucp 55should handle it. 56.Pp 57All systems along the line must have the 58.Nm uusend 59command available and allow remote execution of it. 60.Pp 61Some uucp systems have a bug where binary files cannot be the 62input to a 63.Xr uux 1 64command. If this bug exists in any system along the line, 65the file will show up severely munged. 66.Sh HISTORY 67The 68.Nm 69command appeared in 70.Bx 4.0 . 71