.\" Copyright (c) 1990 The Regents of the University of California.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by the University of
.\" California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" @(#)tftp.1 5.4 (Berkeley) 4/22/91
.Nd trivial file transfer program
is the user interface to the Internet
(Trivial File Transfer Protocol),
which allows users to transfer files to and from a remote machine.
may be specified on the command line, in which case
as the default host for future transfers (see the
is running, it issues the prompt
and recognizes the following commands:
.Bl -tag -width verbose -compact
.It Cm \&? Ar command-name ...
Shorthand for "mode ascii"
Shorthand for "mode binary"
.It Cm connect Ar host-name Op Ar port
does not maintain connections betweeen transfers; thus, the
command does not actually create a connection,
but merely remembers what host is to be used for transfers.
You do not have to use the
command; the remote host can be specified as part of the
.It Cm get Ar remotename localname
.It Cm get Ar file1 file2 ... fileN
Get a file or set of files from the specified
can be in one of two forms:
a filename on the remote host, if the host has already been specified,
to specify both a host and filename at the same time.
If the latter form is used,
the last hostname specified becomes the default for future transfers.
.It Cm mode Ar transfer-mode
Set the mode for transfers;
.It Cm put Ar localfile remotefile
.It Cm put Ar file1 file2 ... fileN remote-directory
Put a file or set of files to the specified
remote file or directory.
can be in one of two forms:
a filename on the remote host, if the host has already been specified,
to specify both a host and filename at the same time.
If the latter form is used,
the hostname specified becomes the default for future transfers.
If the remote-directory form is used, the remote host is
An end of file also exits.
.It Cm rexmt Ar retransmission-timeout
Set the per-packet retransmission timeout, in seconds.
.It Cm timeout Ar total-transmission-timeout
Set the total transmission timeout, in seconds.
Because there is no user-login or validation within
protocol, the remote site will probably have some
sort of file-access restrictions in place. The
exact methods are specific to each site and therefore
difficult to document here.