|
|
1.1 root 1: .TH PUSH 1
2: .CT 1 comm_mach
3: .SH NAME
4: push, pull, npush, npull \- datakit remote file copy
5: .SH SYNOPSIS
6: .B push
7: [
8: .B -v
9: ]
10: .I machine file ... remotedir
11: .PP
12: .B pull
13: [
14: .B -v
15: ]
16: .I machine file ... localdir
17: .PP
18: .B npush
19: [
20: .B -v
21: ]
22: .I machine file ... remotedir
23: .PP
24: .B npull
25: [
26: .B -v
27: ]
28: .I machine file ... localdir
29: .SH DESCRIPTION
30: .I Push
31: and
32: .I pull
33: copy files between machines over Datakit.
34: .I Push
35: copies
36: .I files
37: from the local machine
38: to the directory
39: .I remotedir
40: on the named
41: .I machine.
42: .I Pull
43: copies
44: .I files
45: from the named
46: .I machine
47: to the directory
48: .I localdir
49: on the local machine.
50: The last component of the name of a copy is the same
51: as that of the original.
52: If one of the
53: .I files
54: is a directory, a corresponding
55: directory is created
56: and the directory's files are copied, recursively.
57: .PP
58: Option
59: .B -v
60: announces each file as it is copied.
61: .PP
62: Pushing and pulling involve two programs running in
63: different contexts on different machines.
64: In particular, pulling
65: to directory
66: .L .
67: puts files in the local current directory,
68: but pushing to
69: .L .
70: puts files in the remote home directory.
71: Shell metacharacters which are to be interpreted
72: on the remote machine must be quoted.
73: .PP
74: .I Npush
75: and
76: .I npull
77: behave exactly like
78: .I push
79: and
80: .I pull,
81: but use a different protocol, necessary for communicating
82: to some other Datakit clusters.
83: .SH FILES
84: .TF /usr/lib/Rpush
85: .TP
86: .F /usr/lib/Rpull
87: link to
88: .F /usr/bin/pull
89: for remote end of transaction
90: .TP
91: .F /usr/lib/Rpush
92: link to
93: .F /usr/bin/push
94: .SH SEE ALSO
95: .IR con (1),
96: .IR cp (1),
97: .IR rcp (1),
98: .IR cu (1),
99: .IR uucp (1)
100: .SH DIAGNOSTICS
101: Messages marked
102: .L (remote)
103: are from the sister process running on the
104: remote machine.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.