1 .\" Copyright (c) 1990, 1993, 1994
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)tftp.1 8.2 (Berkeley) 4/18/94
39 .Nd trivial file transfer program
45 is the user interface to the Internet
47 (Trivial File Transfer Protocol),
48 which allows users to transfer files to and from a remote machine.
51 may be specified on the command line, in which case
55 as the default host for future transfers (see the
61 is running, it issues the prompt
63 and recognizes the following commands:
65 .Bl -tag -width verbose -compact
66 .It Cm \&? Ar command-name ...
67 Print help information.
70 Shorthand for "mode ascii"
73 Shorthand for "mode binary"
75 .It Cm connect Ar host-name Op Ar port
86 does not maintain connections between transfers; thus, the
88 command does not actually create a connection,
89 but merely remembers what host is to be used for transfers.
90 You do not have to use the
92 command; the remote host can be specified as part of the
98 .It Cm get Ar filename
99 .It Cm get Ar remotename localname
100 .It Cm get Ar file1 file2 ... fileN
101 Get a file or set of files from the specified
104 can be in one of two forms:
105 a filename on the remote host, if the host has already been specified,
106 or a string of the form
108 to specify both a host and filename at the same time.
109 If the latter form is used,
110 the last hostname specified becomes the default for future transfers.
112 .It Cm mode Ar transfer-mode
113 Set the mode for transfers;
123 .It Cm put Ar localfile remotefile
124 .It Cm put Ar file1 file2 ... fileN remote-directory
125 Put a file or set of files to the specified
126 remote file or directory.
128 can be in one of two forms:
129 a filename on the remote host, if the host has already been specified,
130 or a string of the form
132 to specify both a host and filename at the same time.
133 If the latter form is used,
134 the hostname specified becomes the default for future transfers.
135 If the remote-directory form is used, the remote host is
143 An end of file also exits.
145 .It Cm rexmt Ar retransmission-timeout
146 Set the per-packet retransmission timeout, in seconds.
151 .It Cm timeout Ar total-transmission-timeout
152 Set the total transmission timeout, in seconds.
155 Toggle packet tracing.
162 Because there is no user-login or validation within
165 protocol, the remote site will probably have some
166 sort of file-access restrictions in place. The
167 exact methods are specific to each site and therefore
168 difficult to document here.