Command arguments which have embedded spaces may be quoted with quote `"' marks.
Commands which toggle settings can take an explicit on or off argument to force the setting appropriately.
Commands which take a byte count as an argument (e.g., hash rate and xferbuf support an optional suffix on the argument which changes the interpretation of the argument. Supported suffixes are:
- b
- Causes no modification. (Optional)
- k
- Kilo; multiply the argument by 1024
- m
- Mega; multiply the argument by 1048576
- g
- Giga; multiply the argument by 1073741824
If receives a SIGINFO (see the ``status'' argument of stty(1)) or SIGQUIT signal whilst a transfer is in progress, the current transfer rate statistics will be written to the standard error output, in the same format as the standard completion message.
AUTO-FETCHING FILES
In addition to standard commands, this version of supports an auto-fetch feature. To enable auto-fetch, simply pass the list of hostnames/files on the command line.The following formats are valid syntax for an auto-fetch element:
- [user @ ] host : [path ] [/ ]
-
``Classic''
FTP
- format.
If path contains a glob character and globbing is enabled, (see glob ) then the equivalent of `mget' path is performed.
If the directory component of path contains no globbing characters, it is stored locally with the name basename (see basename(1)) of path in the current directory. Otherwise, the full remote name is used as the local name, relative to the local root directory.
- format.
- ftp:// [user [: password ] @ ] host [: port ] / path [/ ] [;type= X ]
-
- An FTP URL, retrieved using the FTP protocol if set ftp_proxy isn't defined. Otherwise, transfer the URL using HTTP via the proxy defined in set ftp_proxy If set ftp_proxy isn't defined and user is given, login as user In this case, use password if supplied, otherwise prompt the user for one.
If a suffix of `;type=A' or `;type=I' is supplied, then the transfer type will take place as ascii or binary (respectively). The default transfer type is binary.
In order to be compliant with RFC 1738 interprets the path part of an ``ftp://'' auto-fetch URL as follows:
- The `/ ' immediately after the host [: port ] is interpreted as a separator before the path and not as part of the path itself.
- The path is interpreted as a So Li / Sc Ns -separated list of name components. For all but the last such component, performs the equivalent of a cd command. For the last path component, performs the equivalent of a get command.
- Empty name components, which result from `// ' within the path or from an extra `/ ' at the beginning of the path will cause the equivalent of a cd command without a directory name. This is unlikely to be useful.
- Any `% XX ' codes (per RFC 1738 within the path components are decoded, with XX representing a character code in hexadecimal. This decoding takes place after the path has been split into components, but before each component is used in the equivalent of a cd or get command. Some often-used codes are `%2F ' (which represents `/ ' and `%7E ' (which represents `~ '
The above interpretation has the following consequences:
- The path is interpreted relative to the default login directory of the specified user or of the `anonymous' user. If the / directory is required, use a leading path of ``%2F'' If a user's home directory is required (and the remote server supports the syntax), use a leading path of ``%7Euser/'' For example, to retrieve /etc/motd from `localhost' as the user `myname' with the password `mypass' use ``ftp://myname:mypass@localhost/%2fetc/motd''
-
The exact
cd
and
get
commands can be controlled by careful choice of
where to use
`/'
and where to use
`%2F'
(or
`%2f )'
For example, the following URLs correspond to the
equivalents of the indicated commands:
- ftp://host/dir1/dir2/file
- ``cd dir1'' ``cd dir2'' ``get file''
- ftp://host/%2Fdir1/dir2/file
- ``cd /dir1'' ``cd dir2'' ``get file''
- ftp://host/dir1%2Fdir2/file
- ``cd dir1/dir2'' ``get file''
- ftp://host/%2Fdir1%2Fdir2/file
- ``cd /dir1/dir2'' ``get file''
- ftp://host/dir1%2Fdir2%2Ffile
- ``get dir1/dir2/file''
- ftp://host/%2Fdir1%2Fdir2%2Ffile
- ``get /dir1/dir2/file''
- You must have appropriate access permission for each of the intermediate directories that is used in the equivalent of a cd command.
- An FTP URL, retrieved using the FTP protocol if set ftp_proxy isn't defined. Otherwise, transfer the URL using HTTP via the proxy defined in set ftp_proxy If set ftp_proxy isn't defined and user is given, login as user In this case, use password if supplied, otherwise prompt the user for one.
- http:// [user [: password ] @ ] host [: port ] / path
-
- An HTTP URL, retrieved using the HTTP protocol. If set http_proxy is defined, it is used as a URL to an HTTP proxy server. If HTTP authorization is required to retrieve path and `user' (and optionally `password' is in the URL, use them for the first attempt to authenticate.
- file:/// path
-
- A local URL, copied from / path on the local host.
Unless noted otherwise above, and -o output is not given, the file is stored in the current directory as the basename(1) of path Note that if a HTTP redirect is received, the fetch is retried using the new target URL supplied by the server, with a corresponding new path Using an explicit -o output is recommended, to avoid writing to unexpected file names.
If a classic format or an FTP URL format has a trailing `/' or an empty path component, then will connect to the site and cd to the directory given as the path, and leave the user in interactive mode ready for further input. This will not work if set ftp_proxy is being used.
Direct HTTP transfers use HTTP 1.1. Proxied FTP and HTTP transfers use HTTP 1.0.
If -R is given, all auto-fetches that don't go via the FTP or HTTP proxies will be restarted. For FTP this is implemented by using reget instead of get For HTTP this is implemented by using the `Range: bytes=' HTTP/1.1 directive.
If WWW or proxy WWW authentication is required, you will be prompted to enter a username and password to authenticate with.
When specifying IPv6 numeric addresses in a URL, you need to surround the address in square brackets. E.g.: ``ftp://[::1]:21/'' This is because colons are used in IPv6 numeric address as well as being the separator for the port number.
ABORTING A FILE TRANSFER
To abort a file transfer, use the terminal interrupt key (usually Ctrl-C). Sending transfers will be immediately halted. Receiving transfers will be halted by sending an FTP protocol ABOR command to the remote server, and discarding any further data received. The speed at which this is accomplished depends upon the remote server's support for ABOR processing. If the remote server does not support the ABOR command, the prompt will not appear until the remote server has completed sending the requested file.If the terminal interrupt key sequence is used whilst is awaiting a reply from the remote server for the ABOR processing, then the connection will be closed. This is different from the traditional behaviour (which ignores the terminal interrupt during this phase), but is considered more useful.
FILE NAMING CONVENTIONS
Files specified as arguments to commands are processed according to the following rules.- If the file name `- ' is specified, the stdin (for reading) or stdout (for writing) is used.
- If the first character of the file name is `|' the remainder of the argument is interpreted as a shell command. then forks a shell, using popen(3) with the argument supplied, and reads (writes) from the stdout (stdin). If the shell command includes spaces, the argument must be quoted; e.g. ``Qq | ls -lt '' A particularly useful example of this mechanism is: ``dir |more ''
- Failing the above checks, if ``globbing'' is enabled, local file names are expanded according to the rules used in the csh(1); c.f. the glob command. If the command expects a single local file (e.g. put ) only the first filename generated by the "globbing" operation is used.
- For mget commands and get commands with unspecified local file names, the local filename is the remote filename, which may be altered by a case ntrans or nmap setting. The resulting filename may then be altered if runique is on.
- For mput commands and put commands with unspecified remote file names, the remote filename is the local filename, which may be altered by a ntrans or nmap setting. The resulting filename may then be altered by the remote server if sunique is on.
FILE TRANSFER PARAMETERS
The FTP specification specifies many parameters which may affect a file transfer. The type may be one of ``ascii'' ``image'' (binary), ``ebcdic'' and ``local byte size'' (for PDP -10's and PDP -20's mostly). supports the ascii and image types of file transfer, plus local byte size 8 for tenex mode transfers.supports only the default values for the remaining file transfer parameters: mode form and struct
THE .netrc FILE
The .netrc file contains login and initialization information used by the auto-login process. It resides in the user's home directory, unless overridden with the -N netrc option, or specified in the NETRC environment variable. The following tokens are recognized; they may be separated by spaces, tabs, or new-lines:- machine name
- Identify a remote machine name The auto-login process searches the .netrc file for a machine token that matches the remote machine specified on the command line or as an open command argument. Once a match is made, the subsequent .netrc tokens are processed, stopping when the end of file is reached or another machine or a default token is encountered.
- default
-
This is the same as
machine
name
except that
default
matches any name.
There can be only one
default
token, and it must be after all
machine
tokens.
This is normally used as:
default login anonymous password user@site
thereby giving the user an automatic anonymous FTP login to machines not specified in .netrc This can be overridden by using the -n flag to disable auto-login.
- login name
- Identify a user on the remote machine. If this token is present, the auto-login process will initiate a login using the specified name
- password string
- Supply a password. If this token is present, the auto-login process will supply the specified string if the remote server requires a password as part of the login process. Note that if this token is present in the .netrc file for any user other than anonymous will abort the auto-login process if the .netrc is readable by anyone besides the user.
- account string
- Supply an additional account password. If this token is present, the auto-login process will supply the specified string if the remote server requires an additional account password, or the auto-login process will initiate an ACCT command if it does not.
- macdef name
-
Define a macro.
This token functions like the
macdef
command functions.
A macro is defined with the specified name; its contents begin with the
next
.netrc
line and continue until a blank line (consecutive new-line
characters) is encountered.
If a macro named
init
is defined, it is automatically executed as the last step in the
auto-login process.
For example,
default macdef init epsv4 off
followed by a blank line.
COMMAND LINE EDITING
supports interactive command line editing, via the editline(3) library. It is enabled with the edit command, and is enabled by default if input is from a tty. Previous lines can be recalled and edited with the arrow keys, and other GNU Emacs-style editing keys may be used as well.The editline(3) library is configured with a .editrc file - refer to editrc(5) for more information.
An extra key binding is available to to provide context sensitive command and filename completion (including remote file completion). To use this, bind a key to the editline(3) command ftp-complete By default, this is bound to the TAB key.
COMMAND LINE PROMPT
By default, displays a command line prompt of ``ftpGt] '' to the user. This can be changed with the set prompt command.A prompt can be displayed on the right side of the screen (after the command input) with the set rprompt command.
The following formatting sequences are replaced by the given information:
- %/
- The current remote working directory.
- %c [[0 n , ] ] %. [[0 n ] ]
-
- The trailing component of the current remote working directory, or n trailing components if a digit n is given. If n begins with `0' the number of skipped components precede the trailing component(s) in the format Do / Lt] number Gt] trailing Dc (for `%c' or ``... trailing '' (for `%. )'
- %M
- The remote host name.
- %m
- The remote host name, up to the first `.'
- %n
- The remote user name.
- %%
- A single `%'
ENVIRONMENT
uses the following environment variables.- FTPANONPASS
- Password to send in an anonymous FTP transfer. Defaults to ```whoami`@ ''
- FTPMODE
-
Overrides the default operation mode.
Support values are:
- active
- active mode FTP only
- auto
- automatic determination of passive or active (this is the default)
- gate
- gate-ftp mode
- passive
- passive mode FTP only
- FTPPROMPT
- Command-line prompt to use. Defaults to ``ftpGt] '' Refer to Sx COMMAND LINE PROMPT for more information.
- FTPRPROMPT
- Command-line right side prompt to use. Defaults to ``'' Refer to Sx COMMAND LINE PROMPT for more information.
- FTPSERVER
- Host to use as gate-ftp server when gate is enabled.
- FTPSERVERPORT
-
Port to use when connecting to gate-ftp server when
gate
is enabled.
Default is port returned by a
getservbyname ();
lookup of ``ftpgate/tcp'' - FTPUSERAGENT
- The value to send for the HTTP User-Agent header.
- HOME
- For default location of a .netrc file, if one exists.
- NETRC
- An alternate location of the .netrc file.
- PAGER
- Used by various commands to display files. Defaults to more(1) if empty or not set.
- SHELL
- For default shell.
- ftp_proxy
-
URL of
FTP
proxy to use when making
FTP
URL requests
(if not defined, use the standard
FTP
protocol).
See http_proxy for further notes about proxy use.
- http_proxy
-
URL of
HTTP
proxy to use when making
HTTP
URL requests.
If proxy authentication is required and there is a username and
password in this URL, they will automatically be used in the first
attempt to authenticate to the proxy.
If ``unsafe'' URL characters are required in the username or password (for example `@' or `/ )' encode them with RFC 1738 `% XX ' encoding.
Note that the use of a username and password in ftp_proxy and http_proxy may be incompatible with other programs that use it (such as lynx(1)).
NOTE this is not used for interactive sessions, only for command-line fetches.
- no_proxy
- A space or comma separated list of hosts (or domains) for which proxying is not to be used. Each entry may have an optional trailing ":port", which restricts the matching to connections to that port.
EXTENDED PASSIVE MODE AND FIREWALLS
Some firewall configurations do not allow to use extended passive mode. If you find that even a simple ls appears to hang after printing a message such as this:
229 Entering Extended Passive Mode (|||58551|)
then you will need to disable extended passive mode with epsv4 off See the above section Sx The .netrc File for an example of how to make this automatic.
SEE ALSO
getservbyname(3), editrc(5), services(5), ftpd(8)STANDARDS
attempts to be compliant with RFC 959 RFC 1123 RFC 1738 RFC 2068 RFC 2389 RFC 2428 RFC 2732 and draft-ietf-ftpext-mlst-11HISTORY
The command appeared in BSD 4.2Various features such as command line editing, context sensitive command and file completion, dynamic progress bar, automatic fetching of files and URLs, modification time preservation, transfer rate throttling, configurable command line prompt, and other enhancements over the standard BSD were implemented in Nx 1.3 and later releases by An Luke Mewburn Aq lukem@NetBSD.org .
IPv6 support was added by the WIDE/KAME project (but may not be present in all non-NetBSD versions of this program, depending if the operating system supports IPv6 in a similar manner to KAME).
BUGS
Correct execution of many commands depends upon proper behavior by the remote server.An error in the treatment of carriage returns in the BSD 4.2 ascii-mode transfer code has been corrected. This correction may result in incorrect transfers of binary files to and from BSD 4.2 servers using the ascii type. Avoid this problem by using the binary image type.
assumes that all IPv4 mapped addresses Po IPv6 addresses with a form like ::ffff:10.1.1.1 Pc indicate IPv4 destinations which can be handled by AF_INET sockets. However, in certain IPv6 network configurations, this assumption is not true. In such an environment, IPv4 mapped addresses must be passed to AF_INET6 sockets directly. For example, if your site uses a SIIT translator for IPv6-to-IPv4 translation, is unable to support your configuration.
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- AUTO-FETCHING FILES
- ABORTING A FILE TRANSFER
- FILE NAMING CONVENTIONS
- FILE TRANSFER PARAMETERS
- THE .netrc FILE
- COMMAND LINE EDITING
- COMMAND LINE PROMPT
- ENVIRONMENT
- EXTENDED PASSIVE MODE AND FIREWALLS
- SEE ALSO
- STANDARDS
- HISTORY
- BUGS
|
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |