|
|
1.1 root 1:
2:
3:
4: UUSEND(1) 1988 UUSEND(1)
5:
6:
7:
8: NNAAMMEE
9: uusend - send a file to a remote host
10:
11: SSYYNNOOPPSSIISS
12: uuuusseenndd [ --mm mode ] sourcefile sys1!sys2!..!remotefile
13:
14: DDEESSCCRRIIPPTTIIOONN
15: _U_u_s_e_n_d sends a file to a given location on a remote system.
16: The system need not be directly connected to the local sys-
17: tem, but a chain of _u_u_c_p(1) links needs to connect the two
18: systems.
19:
20: If the --mm option is specified, the mode of the file on the
21: remote end will be taken from the octal number given. Oth-
22: erwise, the mode of the input file will be used.
23:
24: The sourcefile can be ``-'', meaning to use the standard
25: input. Both of these options are primarily intended for
26: internal use of _u_u_s_e_n_d.
27:
28: The remotefile can include the ~userid syntax.
29:
30: DDIIAAGGNNOOSSTTIICCSS
31: If anything goes wrong any further away than the first sys-
32: tem down the line, you will never hear about it.
33:
34: SSEEEE AALLSSOO
35: uux(1), uucp(1), uuencode(1)
36:
37: BBUUGGSS
38: This command should not exist, since _u_u_c_p should handle it.
39:
40: All systems along the line must have the _u_u_s_e_n_d command
41: available and allow remote execution of it.
42:
43: Some uucp systems have a bug where binary files cannot be
44: the input to a _u_u_x command. If this bug exists in any sys-
45: tem along the line, the file will show up severly munged.
46:
47:
48:
49:
50:
51:
52:
53:
54:
55:
56:
57:
58:
59:
60:
61:
62:
63: Printed 7/4/90 October 1
64:
65:
66:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.