Commit | Line | Data |
---|---|---|
b28a081b JL |
1 | .TH TFTP 1C "7 February 1986" |
2 | .SH NAME | |
3 | tftp \- trivial file transfer program | |
4 | .SH SYNOPSIS | |
5 | .B tftp | |
6 | [ | |
7 | host | |
8 | ] | |
9 | .SH DESCRIPTION | |
10 | .I Tftp | |
11 | is the user interface to the Internet TFTP | |
12 | (Trivial File Transfer Protocol), | |
13 | which allows users to transfer files to and from a remote machine. | |
14 | The remote | |
15 | .I host | |
16 | may be specified on the command line, in which case | |
17 | .I tftp | |
18 | uses | |
19 | .I host | |
20 | as the default host for future transfers (see the | |
21 | .B connect | |
22 | command below). | |
23 | .SH COMMANDS | |
24 | Once | |
25 | .I tftp | |
26 | is running, it issues the prompt | |
27 | .B tftp> | |
28 | and recognizes the following commands: | |
29 | .TP | |
30 | \fBconnect\fP \fIhost-name\fP [ \fIport\fP ] | |
31 | Set the | |
32 | .I host | |
33 | (and optionally | |
34 | .IR port ) | |
35 | for transfers. | |
36 | Note that the TFTP protocol, unlike the FTP protocol, | |
37 | does not maintain connections betweeen transfers; thus, the | |
38 | .I connect | |
39 | command does not actually create a connection, | |
40 | but merely remembers what host is to be used for transfers. | |
41 | You do not have to use the | |
42 | .I connect | |
43 | command; the remote host can be specified as part of the | |
44 | .I get | |
45 | or | |
46 | .I put | |
47 | commands. | |
48 | .TP | |
49 | \fBmode\fP \fItransfer-mode\fP | |
50 | Set the mode for transfers; | |
51 | .I transfer-mode | |
52 | may be one of | |
53 | .IR ascii | |
54 | or | |
55 | .IR binary . | |
56 | The default is | |
57 | .IR ascii . | |
58 | .TP | |
59 | \fBput\fP \fIfile\fP | |
60 | .TP | |
61 | \fBput\fP \fIlocalfile remotefile\fP | |
62 | .TP | |
63 | \fBput\fP \fIfile1 file2 ... fileN remote-directory\fP | |
64 | Put a file or set of files to the specified | |
65 | remote file or directory. | |
66 | The destination | |
67 | can be in one of two forms: | |
68 | a filename on the remote host, if the host has already been specified, | |
69 | or a string of the form | |
70 | .I host:filename | |
71 | to specify both a host and filename at the same time. | |
72 | If the latter form is used, | |
73 | the hostname specified becomes the default for future transfers. | |
74 | If the remote-directory form is used, the remote host is | |
75 | assumed to be a | |
76 | .I UNIX | |
77 | machine. | |
78 | .TP | |
79 | \fBget\fP \fIfilename\fP | |
80 | .TP | |
81 | \fBget\fP \fIremotename\fP \fIlocalname\fP | |
82 | .TP | |
83 | \fBget\fP \fIfile1\fP \fIfile2\fP ... \fIfileN\fP | |
84 | Get a file or set of files from the specified | |
85 | .IR sources . | |
86 | .I Source | |
87 | can be in one of two forms: | |
88 | a filename on the remote host, if the host has already been specified, | |
89 | or a string of the form | |
90 | .I host:filename | |
91 | to specify both a host and filename at the same time. | |
92 | If the latter form is used, | |
93 | the last hostname specified becomes the default for future transfers. | |
94 | .TP | |
95 | .B quit | |
96 | Exit | |
97 | .IR tftp . | |
98 | .TP | |
99 | .B verbose | |
100 | Toggle verbose mode. | |
101 | .TP | |
102 | .B trace | |
103 | Toggle packet tracing. | |
104 | .TP | |
105 | .B status | |
106 | Show current status. | |
107 | .TP | |
108 | \fBrexmt\fP \fIretransmission-timeout\fP | |
109 | Set the per-packet retransmission timeout, in seconds. | |
110 | .TP | |
111 | \fBtimeout\fP \fItotal-transmission-timeout\fP | |
112 | Set the total transmission timeout, in seconds. | |
113 | .TP | |
114 | .B ascii | |
115 | Shorthand for "mode ascii" | |
116 | .TP | |
117 | .B binary | |
118 | Shorthand for "mode binary" | |
119 | .TP | |
120 | \fB?\fP \ [ \fIcommand-name\fP ... ] | |
121 | Print help information. | |
122 | .SH BUGS | |
123 | .PP | |
124 | Because there is no user-login or validation within | |
125 | the | |
126 | .I TFTP | |
127 | protocol, the remote site will probably have some | |
128 | sort of file-access restrictions in place. The | |
129 | exact methods are specific to each site and therefore | |
130 | difficult to document here. |