|
|
1.1 root 1: .TH UUSEND 1C 6/1/80
2: .UC 4
3: .SH NAME
4: uusend \- send a file to a remote host
5: .SH SYNOPSIS
6: .B uusend
7: [
8: .B \-m
9: mode
10: ]
11: sourcefile
12: sys1!sys2!..!remotefile
13: .SH DESCRIPTION
14: .I Uusend
15: sends a file to a given location on a remote system.
16: The system need not be directly connected to the local
17: system, but a chain of
18: .I uucp(1)
19: links needs to connect the two systems.
20: .PP
21: If the
22: .B \-m
23: option is specified, the mode of the file on the remote
24: end will be taken from the octal number given.
25: Otherwise, the mode of the input file will be used.
26: .PP
27: The sourcefile
28: can be ``\-'',
29: meaning to use the standard input.
30: Both of these options are primarily intended for internal use of uusend.
31: .PP
32: The remotefile can include the ~userid syntax.
33: .SH DIAGNOSTICS
34: If anything goes wrong any further away than the first system down
35: the line, you will never hear about it.
36: .SH SEE\ ALSO
37: uux(1), uucp(1), uuencode(1)
38: .SH AUTHOR
39: Mark Horton
40: .SH BUGS
41: This command shouldn't exist, since
42: .I uucp
43: should handle it.
44: .PP
45: All systems along the line must have the
46: .I uusend
47: command available and allow remote execution of it.
48: .PP
49: Some uucp systems have a bug where binary files cannot be the
50: input to a uux command.
51: If this bug exists in any system along the line,
52: the file will show up severly munged.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.