You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mod_ftp-commits@incubator.apache.org by sc...@apache.org on 2006/11/15 00:04:44 UTC
svn commit: r475070 - in /incubator/mod_ftp/trunk/docs/manual:
ftp/index.html mod/mod_ftp.xml
Author: sctemme
Date: Tue Nov 14 16:04:44 2006
New Revision: 475070
URL: http://svn.apache.org/viewvc?view=rev&rev=475070
Log:
Add all directives from the module source, and most descriptions from the Covalent manual. Add generated index HTML file for ftp directory
Added:
incubator/mod_ftp/trunk/docs/manual/ftp/index.html
Modified:
incubator/mod_ftp/trunk/docs/manual/mod/mod_ftp.xml
Added: incubator/mod_ftp/trunk/docs/manual/ftp/index.html
URL: http://svn.apache.org/viewvc/incubator/mod_ftp/trunk/docs/manual/ftp/index.html?view=auto&rev=475070
==============================================================================
--- incubator/mod_ftp/trunk/docs/manual/ftp/index.html (added)
+++ incubator/mod_ftp/trunk/docs/manual/ftp/index.html Tue Nov 14 16:04:44 2006
@@ -0,0 +1,3 @@
+URI: index.html.en
+Content-Language: en
+Content-type: text/html; charset=ISO-8859-1
Modified: incubator/mod_ftp/trunk/docs/manual/mod/mod_ftp.xml
URL: http://svn.apache.org/viewvc/incubator/mod_ftp/trunk/docs/manual/mod/mod_ftp.xml?view=diff&rev=475070&r1=475069&r2=475070
==============================================================================
--- incubator/mod_ftp/trunk/docs/manual/mod/mod_ftp.xml (original)
+++ incubator/mod_ftp/trunk/docs/manual/mod/mod_ftp.xml Tue Nov 14 16:04:44 2006
@@ -25,162 +25,520 @@
FTP Protocol module for Apache 2.0
-->
-<!--<modulesynopsis> is the root tag and must surround all other tags.
-The sequence of tags is important and must be followed in order for
-the document to validate. -->
-<modulesynopsis>
-
-<!-- module name in lower case; must be identical to base filename -->
-<name>mod_template</name>
-
-<!-- A very short (less than one sentence) description of the
-module; begins with a capital, but does not end with a period, nor
-does it refer to "this module" -->
-<description>Demonstrates the module documentation format</description>
-
-<!-- From:
-http://httpd.apache.org/docs-2.0/mod/module-dict.html#Status -->
-<status>experimental</status>
-
-<!-- As in:
-http://httpd.apache.org/docs-2.0/mod/module-dict.html#SourceFile -->
-<sourcefile>mod_template.c</sourcefile>
-
-<!-- As in:
-http://httpd.apache.org/docs-2.0/mod/module-dict.html#ModuleIdentifier -->
-<identifier>template_module</identifier>
-
-<!-- Optional: as in:
-http://httpd.apache.org/docs-2.0/mod/module-dict.html#Compatibility -->
-<compatibility>Not actually available in any version</compatibility>
-
-
-<summary>
-<!-- Optional but strongly recommended: A one to three paragraph
-summary of what the module does and how to use it. Text cannot be
-placed directly, but rather must be inside paragraphs, examples,
-notes, etc. -->
-
-<p>This is a template and demonstration of the proper documentation format
-for Apache HTTP Server modules.</p>
-
-<example><title>Example</title>
-# Examples are always helpful.<br />
-TemplateDirective On<br />
-</example>
-
-<note type="warning">
-Don't try to actually use this module, since it doesn't exist.
-</note>
-
-</summary>
-
-<!-- References to other documents or directives -->
-<seealso><a href="...">Useful document</a></seealso>
-<seealso><directive module="mod_useful">Useful</directive></seealso>
-<seealso><module>mod_useful</module></seealso>
-
-<!-- Any number of sections may be included below -->
-<section id="moredocs"><title>Additional Documentation</title>
-
-<p>More detailed information about the module in general (as opposed to
-the individual directives) can follow in sections containing titles.</p>
-
-<p>The <code>id</code> attribute will be translated into a hypertext
-anchor target.</p>
-
-<p>References to directives should use the directive tag: <directive
-module="mod_template">TemplateDirective</directive>. References to
-modules should use the module tag
-<module>mod_template.xml</module>.</p>
-
-</section>
-
-
-<directivesynopsis>
-<!-- Exact name of directive in mixed case -->
-<name>TemplateDirective</name>
-
-<!-- A very short (less than one sentence) description of the
-directive; begins with a capital, but does not end with a period -->
-<description>Changes absolutely nothing</description>
-
-<!-- As in:
-http://httpd.apache.org/docs-2.0/mod/directive-dict.html#Syntax -->
-<syntax>TemplateDirective One|Two|Thee <em>file-path</em>
-[<em>env-variable</em>] [<em>env-variable</em>] ...</syntax>
-
-<!-- Optional: Plain text only, exactly as the dirctive would appear in
-the config file, as in:
-http://httpd.apache.org/docs-2.0/mod/directive-dict.html#Default -->
-<default>TemplateDirective Two /usr/local/apache</default>
-
-<!-- Each context as in:
-http://httpd.apache.org/docs-2.0/mod/directive-dict.html#Context
-is placed in a separate context tag -->
-<contextlist><context>Directory</context><context>.htaccess</context>
-</contextlist>
-
-<!-- Required if and only if the contextlist includes .htacccess, as in
-http://httpd.apache.org/docs-2.0/mod/directive-dict.html#Override -->
-<override>FileInfo</override>
-
-<!-- Used only if the same directive is implemented by multiple modules.
-Otherwise, the module will be automatically be grabbed from above. -->
-<modulelist><module>mod_template</module>
-<module>mod_othermodule</module>
-</modulelist>
-
-<!-- Used only if the status for the directive differs from the status
-for the module as a whole. As in:
-http://httpd.apache.org/docs-2.0/mod/directive-dict.html#Status -->
-<status>Experimental</status>
-
-<!-- Optional, as in:
-http://httpd.apache.org/docs-2.0/mod/directive-dict.html#Compatibility -->
-<compatibility>Does not really exist</compatibility>
-
-<!-- Detailed description of what the directive does and how to use it -->
-<usage>
-
-<p>Only the block tags p, example, note, blockquote, ul, and ol can be
-used directly under usage. The pre tag is also allowed, but its use
-is discourage. Inside a paragraph, the tags em, strong, a, code,
-directive, module, and br are allowed.</p>
-
-<p>The directive tag (when the module attribute is given) and the
-module tag automatically create links. For "section" directives like
-<Directory>, a special format is used: <directive module="core"
-type="section">Directory</directive>. The angle brackets will be
-added automatically for display.</p>
-
-<p>The example and note tag have optional <title>s. The note
-tag also has a "type" attribute that can be set to "warning".</p>
-
-<p>All content must be well-formed xml. This means closing tags must
-be used in the correct places, and unclosed tags must be written as such:
-<br />.</p>
-</usage>
-
-<!-- Any number of seealso references can be used for each directive -->
-<seealso><directive module="template.xml">Location</directive></seealso>
-</directivesynopsis>
-
-<!-- If a directive from this module is documented in another module,
-then a special format of the directivesynopsis tag can be used to
-reference it. -->
-<directivesynopsis location="othermodule">
-<name>OtherDirective</name>
-</directivesynopsis>
-
-<!-- If the directive marks a "section" like Directory, Location, etc,
-another special format is used -->
-<directivesynopsis type="section">
-<!-- The angle brackets are *not* included in the name. They will be
-added automatically for display -->
-<name>Location</name>
-<!-- Continue as before -->
-</directivesynopsis>
+<modulesynopsis metafile="mod_ftp.xml.meta" >
+
+ <name>mod_ftp</name>
+ <description>Provides support for the File Transfer Protocol</description>
+ <status>External</status> <!-- For now... -->
+ <sourcefile>mod_ftp.c</sourcefile>
+ <identifier>ftp_module</identifier>
+ <compatibility>Apache 2.3 and higher</compatibility>
+
+ <summary>
+ <p>This module provides support for the File Transfer Protocol
+ within the Apache HTTP Server. It was originally developed by
+ Covalent Technologies, Inc. and contributed by them to the
+ Apache HTTP Server project.</p>
+
+ <p>The FTP protocol module for Apache can work with the access
+ control modules, mod_ssl and any dynamic content generator to
+ provide veratile, scalable and secure FTP services.</p>
+
+ <p>Further details, discussion and examples are provided in the <a
+ href="../ftp/">FTP documentation</a>.</p>
+ </summary>
+
+ <!-- References to other documents or directives -->
+ <seealso><a href="../ftp/">FTP Documentation</a></seealso>
+ <seealso><module>mod_ssl</module></seealso>
+
+ <!-- Any number of sections may be included below -->
+ <section id="moredocs"><title>Additional Documentation</title>
+
+ <p>More detailed information about the module in general (as
+ opposed to the individual directives) can follow in sections
+ containing titles.</p>
+
+ <p>The <code>id</code> attribute will be translated into a hypertext
+ anchor target.</p>
+
+ <p>References to directives should use the directive tag:
+ <directive module="mod_template">TemplateDirective</directive>.
+ References to modules should use the module tag
+ <module>mod_template.xml</module>.</p>
+
+ </section>
+
+ <directivesynopsis>
+ <name>FTP</name>
+ <description>Run an FTP Server on this host</description>
+ <syntax>FTP on|off</syntax>
+ <default>FTP off</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>You must define a <directive>Listen</directive> directive to
+ listen for FTP requests. This directive is <strong>not</strong>
+ inherited from the global configuration file.</p>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPUmask</name>
+ <description>Set the umask for created files</description>
+ <syntax>FTPUmask <em>umask</em></syntax>
+ <default>FTPUmask 022</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive sets the permission mask for file creation
+ access. The default is 022 which gives the owner complete
+ access and disables write access for the group and other
+ users.</p>
+ <note>This directive is inherited to all virtual
+ hosts from the global configuration file.</note>
+ <note>This directive is not supported on Windows.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPDirUmask</name>
+ <description>Set the umask for created directory</description>
+ <syntax>FTPDirUmask <em>umask</em></syntax>
+ <default>Unknown</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <note>Not documented by Covalent</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPTimeoutLogin</name>
+ <description>Idle time allowed when logging in</description>
+ <syntax>FTPTimeoutLogin <em>time</em></syntax>
+ <default>FTPTimeoutLogin 60</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive sets the amount of <em>time</em> in seconds
+ that a user has to send a username to the server. If the
+ username is not received in this amount of time, the user is
+ disconnected.</p>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPTimeoutIdle</name>
+ <description>Idle time allowed during a FTP session</description>
+ <syntax>FTPTimeoutIdle <em>time</em></syntax>
+ <default>FTPTimeoutIdle 600</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive sets the amount of <em>time</em> in seconds
+ allowed between commands sent by the client. If no commands
+ are received in this amount of time, the user is
+ disconnected.</p>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPTimeoutData</name>
+ <description>Idle time allowed during a data transfer</description>
+ <syntax>FTPTimeoutData <em>time</em></syntax>
+ <default>FTPTimeoutData 300</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive sets the <em>time</em> in seconds the server
+ will wait during a data transfer. If no data is sent to the
+ client in this amount of time, the data connection is
+ closed.</p>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPMaxLoginAttempts</name>
+ <description>Maximum number of login attempts</description>
+ <syntax>FTPMaxLoginAttempts <em>attempts</em></syntax>
+ <default>FTPMaxLoginAttempts 3</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive controls the number of failed
+ <em>attempts</em> to log in that are allowed before breaking
+ the connection and logging the failed attempts.</p>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPImplicitSSL</name>
+ <description>Use SSL implicitly</description>
+ <syntax>FTPImplicitSSL on|off</syntax>
+ <default>FTPImplicitSSL off</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive determines the security on the control
+ connection when the user connects. When set to
+ <code>On</code>, the user is expected to connect using SSL.
+ When set to <code>Off</code>, the user must connect insecurely
+ then issue the <code>AUTH</code> command to start a secure
+ session.</p>
+ <note>This directive is <strong>not</strong> inherited from the global
+ configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPOptions</name>
+ <description>Set options for this server</description>
+ <syntax>FTPOptions <em>option1 [option2] ...</em></syntax>
+ <default>None</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive sets per server options.</p>
+ <p>Current options:</p>
+ <dl>
+ <dt><code>RequireSSL</code></dt>
+ <dd><p>This option requires the client to issue an
+ <code>AUTH</code> command to switch to SSL before sending any
+ password information. This is much like implicit SSL in that
+ it forces the client to use SSL to send password information.
+ The difference is that using the <code>RequireSSL</code>
+ option will allow a client to connect without SSL, but then
+ issue the <code>AUTH</code> SSL command before sending the
+ username and password.</p>
+ </dd>
+ <dt><code>CheckMaxClients</code></dt>
+ <dd><p>This option denies login to a client when the server is
+ full. If it is not enabled, the client will wait on the
+ accept queue until another client disconnects.</p>
+ </dd>
+ <dt><code>CreateHomeDirs</code></dt>
+ <dd><p>This option causes the
+ server to automatically create a home directory in the
+ location specified by the
+ <directive>FTPHomeDir</directive> directive. If the
+ <directive>FTPHomeDir</directive> directive is not
+ specified, this option has no effect.</p>
+ <note><p>Setting this option on an anonymous site is not
+ recommended. This is because a directory is created for
+ each unique user (usually identified by their email
+ address) that logs onto the server. </p>
+ <p>This option will only work if the
+ <directive>FTPHomeDir</directive> directories are
+ accessible to the process owner of the Apache HTTP
+ Server, typically on UNIX systems the user
+ <code>nobody</code>.</p>
+ </note>
+ </dd>
+ <dt><code>RemoveUserGroup</code></dt>
+ <dd><p>This option causes the
+ server to print the UID and GID rather than the user name
+ and group name for directory listings. It has no effect on
+ Windows systems.</p>
+ </dd>
+ <dt><code>NLSTShowDirs</code></dt>
+ <dd><p>This option causes the server
+ to display directories as well as files when it receives
+ an <code>NLST</code> request. Some FTP clients send an
+ <code>NLST</code> requests when the user issues an
+ <code>ls</code> or <code>dir</code> commands. Since the
+ default response is to display files only, the user may be
+ confused.</p>
+ <note><p>
+ Setting this option will cause commands that request
+ multiple files to fail and should be used with
+ caution.</p>
+ </note>
+ </dd>
+ <dt><code>NLSTisLIST</code></dt>
+ <dd><p>This option causes the server
+ to display identical output when it receives either a
+ <code>LIST</code> request or an <code>NLST</code> request.
+ Like <directive>NLSTShowDirs</directive>, this option is
+ used for FTP clients that send different requests for
+ <code>ls</code> or <code>dir</code> commands.</p>
+ <note>
+ <p>Setting this option will cause commands that request
+ multiple files to fail and should be used with
+ caution.</p>
+ </note>
+ </dd>
+ <dt><code>LISTisNLST</code></dt>
+ <dd><p>This option causes the server to display identical output
+ when it receives either a <code>LIST</code> request or an
+ <code>NLST</code> request. Unlike
+ <directive>NLSTisLIST</directive>, the output is a list of
+ files without details. If the -l option is passed to
+ <code>LIST</code> requests, details will be provided,
+ whether this option is set or not.</p>
+ </dd>
+ <dt><code>ShowUnAuthorizedFiles</code></dt>
+ <dd><p>This option causes
+ the server to show files that the user does not have
+ authorization to retrieve and directories that the user
+ does not have authorization to enter (<code>cd</code> will
+ fail) when it receives a <code>LIST</code> request. This
+ enables the Covalent Enterprise FTP Server to behave like
+ most standard FTP servers, where users are allowed to list
+ all files and directories, even those they are not allowed
+ to access.</p>
+ </dd>
+ </dl>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPPASVaddr</name>
+ <description>Set the allowed PASV server IP address for the data
+ channel</description>
+ <syntax>FTPPASVAddr <em>IP address</em></syntax>
+ <!-- FIXME Find out what the code does -->
+ <default>Unset</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive allows you to specify a different <em>IP
+ address</em> to be sent on replies to <code>PASV</code> requests.
+ You will find this useful when the FTP Server is behind a
+ firewall.</p>
+ <note>This directive is <strong>not</strong> inherited from the global
+ configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPPASVbindaddr</name>
+ <description>Set and bind the allowed PASV server IP address for
+ the data channel</description>
+ <syntax>FTPPASVbindaddr <em>IP address</em></syntax>
+ <!-- FIXME Ditto FTPPASVaddr -->
+ <default>Unset</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive is identical to
+ <directive>FTPPASVaddr</directive> except that the Apache FTP
+ Server attempts to bind to the specified
+ <em>IP address</em>.</p>
+ <note>This directive is <strong>not</strong> inherited from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPPASVrange</name>
+ <description>Set the allowed PASV port range</description>
+ <syntax>FTPPASVrange <em>number number</em></syntax>
+ <!-- FIXME Find out what the code does: this is probably the
+ default behaviour when binding to an unspecified port, and will
+ vary by platform and OS. -->
+ <default>Unset</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive defines the port range (<em>number</em> to
+ <em>number</em> inclusive) to be used for passive connections.
+ This directive is designed for use in environments where you
+ only want to open a specific range of ports on your
+ firewall.</p>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPBannerMessage</name>
+ <description>Set initial login message</description>
+ <syntax>FTPBannerMessage
+ <em>message</em>|<em>file:/path/to/file</em></syntax>
+ <default>Unset</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <p>This directive sets a <em>message</em> that is displayed to
+ the client on initial connection. This can either be a string,
+ or a path to a file. The message can contain a variety of
+ meta-characters:</p>
+ <ul>
+ <li><code>%T</code><p>Local time (in the form <code>Mon Apr 29
+ 20:36:48 2002</code>)</p></li>
+ <li><code>%C</code><p>Current working directory</p></li>
+ <li><code>%h</code><p>Remote host</p></li>
+ <li><code>%L</code><p>Local host</p></li>
+ <li><code>%E</code><p>Server administrator (as given by
+ <directive>ServerAdmin</directive>)</p></li>
+ <li><code>%a</code><p>Remote IP-address</p></li>
+ <li><code>%A</code><p>Local IP-address</p></li>
+ <li><code>%u</code><p>Remote user</p></li>
+ <li><code>%f</code><p>Number of files transferred</p></li>
+ <li><code>%t</code><p>Total number of bytes downloaded</p></li>
+ <li><code>%x</code><p>Number of data transfers</p></li>
+ <li><code>%b</code><p>Total traffic for the session (both
+ control and data)</p></li>
+ </ul>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPExitMessage</name>
+ <description>Set logout message</description>
+ <syntax>FTPExitMessage
+ <em>message</em>|<em>file:/path/to/file</em></syntax>
+ <default></default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage><p>This directive sets a <em>message</em> that is displayed to
+ the client on disconnect. This can either be a string, or a
+ path to a file. The message can contain a variety of
+ meta-characters (see
+ <directive>FTPBannerMessage</directive>.</p>
+ <note>This directive is inherited to all virtual hosts from the
+ global configuration file.</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPHomeDir</name> <description>Set the path to directory
+ containing user's home directories</description>
+ <syntax>FTPHomeDir /directory</syntax>
+ <default>Unset</default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage><p>This directive defines where the user home <em>directory</em>
+ is located. This directory must be given as an absolute path,
+ but is actually relative to the configured
+ <directive>DocumentRoot</directive> for the server. For
+ example, <code>FTPHomeDir /home</code> will cause the Apache FTP
+ Server to look for the user home in the directory
+ <directive>DocumentRoot</directive><code>/home/</code><code>username</code>
+ (where <em>username</em> is the login name of the user).</p>
+ <p>If <directive>FTPHomeDir</directive> has been specified and
+ the home directory for the user does not exist, the server logs
+ an error and user is logged into the root
+ ("<code>/</code>") directory. If you want the home
+ directory created automatically, see the
+ <directive>CreateHomeDirs</directive> option to the
+ <directive>FTPOptions</directive> directive.</p>
+ </usage>
+ <note>This directive is <strong>not</strong> inherited from the
+ global configuration file.</note>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPDocRootEnv</name>
+ <description>Set the DocumentRoot based on the given environment
+ variable, such as a per-user LDAP property</description>
+ <syntax></syntax>
+ <default></default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPJailUser</name>
+ <description>Users are not allowed to leave their home
+ directories</description>
+ <syntax></syntax>
+ <default></default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPActiveRange</name>
+ <description>Ports the server will use for connecting to the
+ client</description>
+ <syntax></syntax>
+ <default></default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPReadmeMessage</name>
+ <description>Set per-directory Readme file</description>
+ <syntax></syntax>
+ <default></default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context><context>.htaccess</context></contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPLimitLoginUser</name>
+ <description>Set the maximum number of concurrent logins per
+ user</description>
+ <syntax></syntax>
+ <default></default>
+ <!-- This directive is allowed in RSRC_CONF, which is not in line
+ with Covalent documentation -->
+ <contextlist><context>server config</context>
+ </contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPLimitLoginIP</name>
+ <description>Set the maximum number of concurrent logins per IP
+ address</description>
+ <syntax></syntax>
+ <default></default>
+ <contextlist><context>server config</context>
+ <context>virtual host</context></contextlist>
+ <usage>
+ <note>Not documented by Covalent</note>
+ </usage>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPLimitLoginServer</name>
+ <description>Set the maximum number of concurrent logins per
+ server</description>
+ <syntax></syntax>
+ <default></default>
+ <!-- This directive is allowed in RSRC_CONF, which is not in line
+ with Covalent documentation -->
+ <contextlist><context>server config</context>
+ </contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPLimitDBFile</name>
+ <description>Set the location for the Login Limit DB file</description>
+ <syntax></syntax>
+ <default></default>
+ <!-- This directive is allowed in RSRC_CONF, which is not in line
+ with Covalent documentation -->
+ <contextlist><context>server config</context>
+ </contextlist>
+ </directivesynopsis>
+
+ <directivesynopsis>
+ <name>FTPDataBlockSize</name>
+ <description>Block size in bytes to use during data transfers</description>
+ <syntax></syntax>
+ <default></default>
+ <!-- This directive is allowed in RSRC_CONF, which is not in line
+ with Covalent documentation -->
+ <contextlist><context>server config</context>
+ </contextlist>
+ <usage>
+ <note>Not documented by Covalent</note>
+ </usage>
+ </directivesynopsis>
</modulesynopsis>