Menu
▾
▴
[Proftpd-docs] www.proftpd.org/docs/howto DSO.html, 1.4, 1.5 FTP.html, 1.1, 1.2
|
From: TJ S. <cas...@us...> - 2012-10-12 15:23:20
|
Update of /cvsroot/pdd/www.proftpd.org/docs/howto In directory vz-cvs-3.sog:/tmp/cvs-serv13755 Modified Files: DSO.html FTP.html Log Message: Updating website copy of docs. Index: DSO.html =================================================================== RCS file: /cvsroot/pdd/www.proftpd.org/docs/howto/DSO.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- DSO.html 3 Aug 2012 18:24:30 -0000 1.4 +++ DSO.html 12 Oct 2012 15:23:16 -0000 1.5 @@ -327,6 +327,53 @@ its own <code>configure</code> script and <code>Makefile</code>, then you should use those. Otherwise, <code>prxs</code> should suffice. +<p><a name="FAQ"> +<b>Frequently Asked Questions</b><br> +<font color=red>Question</font>: My installed <code>proftpd</code> does not +include <code>mod_sql_passwd</code> (or some other module). How can I get +proftpd to use this module without recompiling?<br> +<font color=blue>Answer</font>: First, see if your proftpd package came +with the <a href="#prxs"><code>prxs</code></a> tool; by default, this tool +is installed as <code>/usr/local/bin/prxs</code>. If you do not find +<code>prxs</code> anywhere on your system, you will have to recompile proftpd +in order to add new modules. + +<p> +Second, you will need the source code for <code>mod_sql_passwd</code> (or +whatever other module you want to add to your proftpd). Assume, then, that +you have found the <code>mod_sql_passwd.c</code> source file. The next +step is to use <code>prxs</code> to build that module as a DSO module: +<pre> + # /usr/local/bin/prxs -c -i -d mod_sql_passwd.c +</pre> +If the above fails with this error message: +<pre> + Your installed proftpd does not support shared modules/DSOs. + Make sure the --enable-dso configure option is used when + compiling proftpd. +</pre> +It means that your <code>proftpd</code> does not have DSO support -- and +that means that you will have to recompile proftpd to add the new module. + +<p> +If, on the other hand, your <code>prxs</code> succeeded, the last steps are +to update your <code>proftpd.conf</code> to load the new module, and then +restart proftpd so that it reads the updated configuration. Continuing with +the example of <code>mod_sql_passwd</code>, you would add the following line +near the top of your <code>proftpd.conf</code>: +<pre> + LoadModule mod_sql_passwd.c +</pre> +and later in the config file, configure your newly added module: +<pre> + <IfModule mod_sql_passwd.c> + SQLPasswordEngine on + ... + </IfModule> +</pre> +Last, restart proftpd, and enjoy your new module's functionality, all without +needing to recompile/reinstall proftpd itself. + <p> <hr> <i>$Date$</i><br> Index: FTP.html =================================================================== RCS file: /cvsroot/pdd/www.proftpd.org/docs/howto/FTP.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -d -r1.1 -r1.2 --- FTP.html 17 Aug 2007 00:11:26 -0000 1.1 +++ FTP.html 12 Oct 2012 15:23:16 -0000 1.2 @@ -19,13 +19,17 @@ </li> <p> + <li><a name="ALLO"><b><code>ALLO</code></b></a><br> + </li> + + <p> <li><a name="APPE"><b><code>APPE</code></b></a><br> Short for <b>APPE</b>nd.<br> </li> <p> <li><a name="AUTH"><b><code>AUTH</code></b></a><br> - Short for <b>AUTH</b>enticate (supported by <code>mod_tls</code>)<br> + Short for <b>AUTH</b>enticate (supported by <a href="../contrib/mod_tls.html"><code>mod_tls</code></a>)<br> </li> <p> @@ -71,6 +75,10 @@ </li> <p> + <li><a name="LANG"><b><code>LANG</code></b></a><br> + </li> + + <p> <li><a name="LIST"><b><code>LIST</code></b></a><br> </li> @@ -78,10 +86,20 @@ <li><a name="MDTM"><b><code>MDTM</code></b></a><br> Short for <b>M</b>o<b>D</b>ification <b>T</b>i<b>M</b>e, this command is used by the client to request the modification time of a file on the - server. This command is not defined in any formal RFCs (yet), but is - a commonly implemented FTP command. <i>Note</i> that this command - <b>cannot</b> be used to change the modification time of the file on - the server; it only reports on the file's modification time.<br> + 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. + <i>Note</i> that this command <b>cannot</b> be used to change the + modification time of the file on the server; it only <i>reports</i> on the + file's modification time. The <a href="#MFMT"><code>MFMT</code></a> + command is used to <i>change</i> a file's modification time.<br> + </li> + + <p> + <li><a name="MFMT"><b><code>MFMT</code></b></a><br> + Short for <b>M</b>odify <b>F</b>act: Last <b>M</b>odified <b>T</b>ime, + 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> <p> @@ -90,6 +108,32 @@ </li> <p> + <li><a name="MLSD"><b><code>MLSD</code></b></a><br> + Short for <b>M</b>achine <b>L</b>i<b>S</b>ting, <b>D</b>irectory, 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> + + <p> + <li><a name="MLST"><b><code>MLST</code></b></a><br> + Short for <b>M</b>achine <b>L</b>i<b>ST</b>ing, 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 <b>is for a single file only</b>. + </li> + + <p> + <li><a name="MODE"><b><code>MODE</code></b></a><br> + 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>i.e.</i> <b>S</b>tream). + </li> + + <p> <li><a name="NLST"><b><code>NLST</code></b></a><br> Short for <b>N</b>ame <b>L</b>i<b>ST</b>.<br> </li> @@ -342,10 +386,6 @@ </li> <p> - <li><a name="ALLO"><b><code>ALLO</code></b></a><br> - </li> - - <p> <li><a name="MACB"><b><code>MACB</code></b></a><br> Short for <b>MAC</b>intosh <b>B</b>inary. This command is not defined in any RFC, and is something of a hack added by Apple in order to support @@ -353,13 +393,6 @@ </li> <p> - <li><a name="MODE"><b><code>MODE</code></b></a><br> - There are three mode types defined by RFC959; <code>proftpd</code> only - supports one (<i>i.e.</i> <b>S</b>tream), and thus this command is not - supported.<br> - </li> - - <p> <li><a name="REIN"><b><code>REIN</code></b></a><br> </li> |