Gecko [ www.thearyasamaj.org ]

Name	Size	Permission
ASCII.html	3.71 KB	-rw-r--r--
AWS.html	26.05 KB	-rw-r--r--
AuthFiles.html	9.54 KB	-rw-r--r--
Authentication.html	15.32 KB	-rw-r--r--
BCP.html	13.7 KB	-rw-r--r--
Chroot.html	14.27 KB	-rw-r--r--
Classes.html	5.92 KB	-rw-r--r--
Compiling.html	34.11 KB	-rw-r--r--
ConfigFile.html	16.47 KB	-rw-r--r--
ConfigurationTricks.html	16.54 KB	-rw-r--r--
ConnectionACLs.html	6.84 KB	-rw-r--r--
Controls.html	11.95 KB	-rw-r--r--
CreateHome.html	7.79 KB	-rw-r--r--
DNS.html	6.92 KB	-rw-r--r--
DSO.html	14.9 KB	-rw-r--r--
Debugging.html	12.47 KB	-rw-r--r--
Directory.html	10.89 KB	-rw-r--r--
DisplayFiles.html	6.69 KB	-rw-r--r--
ECCN.html	4.73 KB	-rw-r--r--
FTP.html	16.09 KB	-rw-r--r--
FXP.html	5.57 KB	-rw-r--r--
Filters.html	7.93 KB	-rw-r--r--
Globbing.html	5.53 KB	-rw-r--r--
KeepAlives.html	19.68 KB	-rw-r--r--
Limit.html	15.08 KB	-rw-r--r--
ListOptions.html	6.18 KB	-rw-r--r--
LogLevels.html	5.08 KB	-rw-r--r--
LogMessages.html	14.89 KB	-rw-r--r--
Logging.html	22.37 KB	-rw-r--r--
Memcache.html	9.04 KB	-rw-r--r--
NAT.html	11.15 KB	-rw-r--r--
Nonroot.html	4.23 KB	-rw-r--r--
Quotas.html	17.17 KB	-rw-r--r--
Radius.html	17.35 KB	-rw-r--r--
Redis.html	8.53 KB	-rw-r--r--
Regex.html	22.23 KB	-rw-r--r--
Rewrite.html	16.8 KB	-rw-r--r--
SQL.html	40.55 KB	-rw-r--r--
SSH.html	5.14 KB	-rw-r--r--
Scoreboard.html	9.11 KB	-rw-r--r--
Sendfile.html	7.34 KB	-rw-r--r--
ServerType.html	10.45 KB	-rw-r--r--
Stopping.html	10.31 KB	-rw-r--r--
TLS.html	58.93 KB	-rw-r--r--
Testing.html	8.73 KB	-rw-r--r--
Timestamps.html	6.71 KB	-rw-r--r--
Tracing.html	8.68 KB	-rw-r--r--
Translations.html	3.52 KB	-rw-r--r--
Umask.html	9.16 KB	-rw-r--r--
Upgrade.html	2.14 KB	-rw-r--r--
Versioning.html	5.41 KB	-rw-r--r--
Vhost.html	11.55 KB	-rw-r--r--
VirtualUsers.html	8.8 KB	-rw-r--r--
ftpaccess.html	2.03 KB	-rw-r--r--
index.html	10.45 KB	-rw-r--r--

Code Editor : FTP.html

<!DOCTYPE html>
<html>
<head>
<title>ProFTPD: Supported FTP Commands</title>
</head>

<hr>
<center><h2>ProFTPD: Supported FTP Commands</h2></center>
<hr>

Supported FTP Commands 
<ul>
 <li><a name="ABOR"><code>ABOR</code></a> 
 </li>

<li><a name="ALLO"><code>ALLO</code></a> 
 Short for ALLOcate. 
 </li>

<li><a name="APPE"><code>APPE</code></a> 
 Short for APPEnd. 
 </li>

<li><a name="AUTH"><code>AUTH</code></a> 
 Short for AUTHenticate (supported by <a href="../contrib/mod_tls.html"><code>mod_tls</code></a>) 
 </li>

<li><a name="CDUP"><code>CDUP</code></a> 
 Short for Change Directory UP, this command is used
 to move the client's &quot;location&quot; on the server up one level in
 the filesystem hierarchy. 
 </li>

<li><a name="CLNT"><code>CLNT</code></a> 
 Short for CLieNT, this command is used by clients to
 offer/provide any freeform identification they desire to the server.
 </li>

<li><a name="CWD"><code>CWD</code></a> 
 Short for Change Working Directory. 
 </li>

<li><a name="DELE"><code>DELE</code></a> 
 Short for DELEte, this command is used by the client to tell the
 server to delete a file. 
 </li>

<li><a name="EPRT"><code>EPRT</code></a> 
 Short for Extended PoRT, an enhanced version of
 the <a href="#PORT"><code>PORT</code></a> command that can handle IPv6
 addresses. 
 </li>

<li><a name="EPSV"><code>EPSV</code></a> 
 Short for Extended PaSsiVe, an enhanced
 version of the <a href="#PASV"><code>PASV</code></a> command that can
 handle IPv6 addresses. 
 </li>

<li><a name="FEAT"><code>FEAT</code></a> 
 Short for FEATures, this command is used by the client to request
 a descriptive list of server-supported features. 
 </li>

<li><a name="HASH"><code>HASH</code></a> 
 This command is used by clients to request the checksum, or "hash", of
 a file on the server. This command is available when the
 <a href="../contrib/mod_digest.html"><code>mod_digest</code></a> module
 is compiled/loaded. 
 </li>

<li><a name="HOST"><code>HOST</code></a> 
 This command is the equivalent of HTTP's "Host" header for FTP, providing
 the ability to have name-based virtual hosting.
 </li>

<li><a name="MDTM"><code>MDTM</code></a> 
 Short for MoDification TiMe, this command
 is used by the client to request the modification time of a file on the
 server. This command is defined formally in <a href="http://www.faqs.org/rfcs/rfc3659.html">RFC 3659</a>, and is a commonly implemented FTP command.
 Note that this command cannot be used to change the
 modification time of the file on the server; it only reports on the
 file's modification time. The <a href="#MFMT"><code>MFMT</code></a>
 command is used to change a file's modification time. 
 </li>

<li><a name="MFMT"><code>MFMT</code></a> 
 Short for Modify Fact: Last Modified Time,
 supported by <a href="../modules/mod_facts.html"><code>mod_facts</code></a>.
 Some clients use this command to change the last modified timestamp on
 a newly uploaded file so that the timestamp on the server matches the
 timestamp of that file on the client.
 </li>

<li><a name="MKD"><code>MKD</code></a> 
 Short for MaKe Directory. 
 </li>

<li><a name="MLSD"><code>MLSD</code></a> 
 Short for Machine LiSting, Directory, supported
 by <a href="../modules/mod_facts.html"><code>mod_facts</code></a>. Unlike
 the <a href="#LIST"><code>LIST</code></a> command, whose response format
 was never specified, the <code>MLSD</code> command has a strictly defined
 response format (see <a href="http://www.faqs.org/rfcs/rfc3659.html">RFC 3659</a> for details). This format was designed to be easily machine parseable,
 for automated processing of directory listing formats; the format was also
 designed to be platform-agnostic, and thus portable.
 </li>

<li><a name="MLST"><code>MLST</code></a> 
 Short for Machine LiSTing, supported by
 <a href="../modules/mod_facts.html"><code>mod_facts</code></a>. This
 command is similar to <a href="#MLSD"><code>MLSD</code></a> in that it
 uses the same response format. Unlike <code>MLSD</code>, the response for a
 <code>MLST</code> is sent back on the control connection rather than
 using a data connection, and is for a single file only.
 </li>

<li><a name="MODE"><code>MODE</code></a> 
 There are three mode types defined by <a href="http://www.faqs.org/rfcs/rfc969.html">RFC 959</a>; <code>proftpd</code> only supports one (i.e. Stream).
 </li>

<li><a name="NLST"><code>NLST</code></a> 
 Short for Name LiST. 
 </li>

<li><a name="NOOP"><code>NOOP</code></a> 
 Short for NO OPeration. This command has no functionality, and
 is often used as a session keepalive mechanism. 
 </li>

<li><a name="OPTS"><code>OPTS</code></a> 
 Short for OPTionS. This command is used to specify
 optional parameters for the command to follow the <code>OPTS</code>
 command, if that command supports such optional parameters. 
 </li>

<li><a name="PASS"><code>PASS</code></a> 
 Short for PASSword, the client uses this command to convey the
 password of the user attempting to log into the server. 
 </li>

<li><a name="PASV"><code>PASV</code></a> 
 Short for PASsiVe, the client uses this command to ask the
 server for a port to which the client should connect, indicating a
 passive data transfer. 
 </li>

<li><a name="PBSZ"><code>PBSZ</code></a> 
 Short for Protection Buffer SiZe. Used
 to determine the size of a buffer needed for secure handshaking (supported
 by <a href="../contrib/mod_tls.html"><code>mod_tls</code></a>) 
 </li>

<li><a name="PORT"><code>PORT</code></a> 
 The client uses this command to tell the server to what client-side port
 the server should contact; use of this command indicates an active data
 transfer. 
 </li>

<li><a name="PROT"><code>PROT</code></a> 
 Short for PROTection. Used to set the protection level on the
 data channel (supported by
 <a href="../contrib/mod_tls.html"><code>mod_tls</code></a>) 
 </li>

<li><a name="PWD"><code>PWD</code></a> 
 Short for Print Working Directory. 
 </li>

<li><a name="REST"><code>REST</code></a> 
 Short for RESTart, this command is used by the client to tell the
 server that it would like to restart a previous data transfer, either
 upload or download. 
 </li>

<li><a name="RETR"><code>RETR</code></a> 
 Short for RETRieve, this command is used by the client to inform
 the server of the file the client would like to download. On many FTP
 client, this is implemented using the client-specfic &quot;get&quot;
 command. 
 </li>

<li><a name="RMD"><code>RMD</code></a> 
 Short for ReMove Directory, this command is used
 to have the server delete the requested directory from its filesystem. 
 </li>

<li><a name="RNFR"><code>RNFR</code></a> 
 Short for ReName FRom. 
 </li>

<li><a name="RNTO"><code>RNTO</code></a> 
 Short for ReName TO. 
 </li>

<li><a name="SITE"><code>SITE</code></a> 
 This command is used for site-specific commands. See below for descriptions
 of <code>proftpd</code>'s SITE commands. 
 </li>

<li><a name="STOR"><code>STOR</code></a> 
 Short for STORe, this command is used by the client to tell the
 the server that the client will be uploading data for a file to stored
 on the server using the filename given. On many FTP clients, this
 is implemented using the client-specific &quot;put&quot; command. 
 </li>

<li><a name="STOU"><code>STOU</code></a> 
 Short for STOre Uunique, it requests that the file being
 stored on the server be given a unique filename. The server chooses the
 unique name for the stored file, and reports the name chosen back to
 the client. On some FTP clients, this ability is enabled using the
 client-specific &quot;sunique&quot; command. 
 </li>

<li><a name="USER"><code>USER</code></a> 
 An FTP client uses this command to inform the server of the name of the
 user requesting an FTP session. 
 </li>

<li><a name="XCUP"><code>XCUP</code></a> 
 This is an X-variant of the <a href="#CDUP"><code>CDUP</code></a> command,
 and has the same functionality. 
 </li>

<li><a name="XCWD"><code>XCWD</code></a> 
 This is an X-variant of the <a href="#CWD"><code>CWD</code></a> command,
 and has the same functionality. 
 </li>

<li><a name="XMKD"><code>XMKD</code></a> 
 This is an X-variant of the <a href="#MKD"><code>MKD</code></a> command,
 and has the same functionality. 
 </li>

<li><a name="XPWD"><code>XPWD</code></a> 
 This is an X-variant of the <a href="#PWD"><code>PWD</code></a> command,
 and has the same functionality. 
 </li>

<li><a name="XRMD"><code>XRMD</code></a> 
 This is an X-variant of the <a href="#RMD"><code>RMD</code></a> command,
 and has the same functionality. 
 </li>
</ul>

Supported <code>SITE</code> commands 
<ul>
 <li><a name="SITE_CHGRP"><code>CHGRP</code></a> 
 Short for CHange GRouP.
 
 Example:
<pre>
 SITE CHGRP ftpgroup script.cgi
</pre>
 </li>

<li><a name="SITE_CHMOD"><code>CHMOD</code></a> 
 Short for CHange MODe.
 
 Example:
<pre>
 SITE CHMOD 755 script.cgi
</pre>
 </li>

<li><a name="SITE_MKDIR"><code>MKDIR</code></a> 
 Similar to the <a href="#MKD"><code>MKD</code></a> command, this
 <code>SITE</code> can be used to create a directory. It will, unlike
 <code>MKD</code>, also create any directories in the path that do
 not exist.
 
 Example:
<pre>
 SITE MKDIR /path/to/some/dir/that/is/not/there/
</pre>
 Supported by the <a href="../contrib/mod_site_misc.html"><code>mod_site_misc</code></a> module.
 </li>

<li><a name="SITE_RMDIR"><code>RMDIR</code></a> 
 Similar to the <a href="#RMD"><code>RMD</code></a> command, this
 <code>SITE</code> can be used to remove a directory. It will, unlike
 <code>RMD</code>, also delete any files in the directory.
 
 Example:
<pre>
 SITE RMDIR /path/to/some/dir/with/files/
</pre>
 Supported by the <a href="../contrib/mod_site_misc.html"><code>mod_site_misc</code></a> module.
 </li>

<li><a name="SITE_SYMLINK"><code>SYMLINK</code></a> 
 Used to create a symbolic link (a.k.a. a symlink) from
 the source path (src) to the destination path (dest).
 
 Example:
<pre>
 SITE SYMLINK src dest
</pre>
 Supported by the <a href="../contrib/mod_site_misc.html"><code>mod_site_misc</code></a> module.
 </li>

<li><a name="SITE_UTIME"><code>UTIME</code></a> 
 Used to update the access and modification timestamps on a file.
 
 Example:
<pre>
 SITE UTIME 200412312359 /path/to/some/file.txt
</pre>
 Supported by the <a href="../contrib/mod_site_misc.html"><code>mod_site_misc</code></a> module.
 </li>
</ul>

Unsupported FTP Commands 
<ul>
 <li><a name="ACCT"><code>ACCT</code></a> 
 Short for ACCounT 
 </li>

<li><a name="MACB"><code>MACB</code></a> 
 Short for MACintosh Binary. This command is not defined in
 any RFC, and is something of a hack added by Apple in order to support
 transfers of the resource forks of Mac files. 
 </li>

<li><a name="STRU"><code>STRU</code></a> 
 Short for STRUcture. <code>proftpd</code> only supports a
 <code>STRU</code> parameter of type F (for &quot;file&quot;),
 and so does not support this command. 
 </li>
</ul>

<a name="FAQ">
Frequently Asked Questions

<a name="MoveDirectoriesAcrossDevices">
Question: I can use the <code>RNFR</code> and
<code>RNTO</code> commands to move a file, even across different
disks/mount points. And I can use <code>RNFR</code>/<code>RNTO</code> to move
a directory, but I cannot move a directory across different
disks/mount points. Is this a bug? 
Answer: No, it is not a bug. Why not? Ultimately,
it is because the FTP specifications do not guarantee (or even discuss)
that an FTP implementation must support renaming of directories across
mount points.

ProFTPD implements the <code>RNFR</code>/<code>RNTO</code> functionality
by using the <code>rename(2)</code> system call. And <code>rename(2)</code>
is documented to not work across mount points.

"But then why does it work when I rename a file across mount points?" you
ask. Good question. The answer is that for files only, ProFTPD
detects the <code>rename(2)</code> error for renaming across mount points,
and then copies the file in question to the new location, deleting
the old location when the copy completes successfully.

"Great!" you say, "Now do the same thing for directories!" Unfortunately, for
directories, the answer is not that simple. Here are some things to consider
when copying directories: what if the directory contains sockets, FIFOs,
devices, and other irregular file types which cannot be easily copied/moved?
Should copying/moving of directories automatically use root privileges in
order to preserve the ownership on files that do not belong to the logged-in
user? What if the copying/deleting of files fails in the midde: what should
then happen to the copied (and remaining) files/directories?

Since there are no easy answers as yet to the above questions, ProFTPD now
detects the <code>rename(2)</code> error for renaming across mount points
for a directory, and rejects the <code>RNTO</code> command, showing
something like:
<pre>
 RNFR directory
 350 File or directory exists, ready for destination name
 RNTO /other/mount/directory
 550 Rename /other/mount/directory: Is a directory
</pre>
That "Is a directory" error indicates that ProFTPD cannot rename a directory
across the mount points you requested. (That particular error message can,
and will, be made more informative.)

</body>
</html>

${this.title}

Code Editor : FTP.html