Menu
▾
▴
[Proftpd-docs] www.proftpd.org/docs/modules mod_facts.html, 1.2, 1.3
|
From: TJ S. <cas...@us...> - 2012-07-31 20:36:50
|
Update of /cvsroot/pdd/www.proftpd.org/docs/modules In directory vz-cvs-3.sog:/tmp/cvs-serv10055 Modified Files: mod_facts.html Log Message: Updating website copy of the mod_facts documentation. Index: mod_facts.html =================================================================== RCS file: /cvsroot/pdd/www.proftpd.org/docs/modules/mod_facts.html,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- mod_facts.html 9 Nov 2011 23:52:11 -0000 1.2 +++ mod_facts.html 31 Jul 2012 20:36:48 -0000 1.3 @@ -41,6 +41,7 @@ <h2>Directives</h2> <ul> <li><a href="#FactsAdvertise">FactsAdvertise</a> + <li><a href="#FactsOptions">FactsOptions</a> </ul> <hr> @@ -63,7 +64,7 @@ <code>LIST</code>/<code>NLST</code> commands. Some FTP clients, though, will attempt to use the newer commands just as if they were equivalent to the older commands, including supporting glob/wildcard characters. -Section 2.2.2 of RFC3659 explicitly states that wildcard characters are +Section 2.2.2 of RFC3659, which explicitly states that wildcard characters are <b>not</b> supported in the <code>MLSD</code> and <code>MLST</code> commands. Thus, to prevent problems when using such FTP clients with proftpd, you can disable the advertising of support for those commands using @@ -74,6 +75,39 @@ </IfModule> </pre> +<hr> +<h2><a name="FactsOptions">FactsOptions</a></h2> +<strong>Syntax:</strong> FactsOptions <em>opt1 ...</em><br> +<strong>Default:</strong> None<br> +<strong>Context:</strong> server config, <code><VirtualHost></code>, <code><Global></code><br> +<strong>Module:</strong> mod_facts<br> +<strong>Compatibility:</strong> 1.3.4b and later + +<p> +The <code>FactsOptions</code> directive is used to configure various optional +behavior of <code>mod_facts</code>. <b>Note</b>: all of the configured +<code>FactsOptions</code> parameters <b>must</b> appear on the same line in the +configuration; only the <i>first</i> <code>FactsOptions</code> directive that +appears in the configuration is used. + +<p> +The currently implemented options are: +<ul> + <li><code>UseSlink</code><br> + <p> + Use this option to have <code>mod_facts</code> use the <i>broken</i> + "OS.unix=slink" syntax, preferred by FTP clients such as FileZilla, for + indicating symlinks, rather than the more correct "OS.unix=symlink" + syntax. See + <a href="http://bugs.proftpd.org/show_bug.cgi?id=3318">Bug#3318</a> for + a more detailed discussion. + + <p> + <b>Note</b> that this option first appeared in + <code>proftpd-1.3.4b</code>. + </li> +</ul> + <p><a name="FAQ"> <b>Frequently Asked Questions</b><br> @@ -81,7 +115,7 @@ <font color=red>Question</font>: Why does <code>MLSD</code> list all of the files in a directory, including the "hidden" files, where the <code>LIST</code> command does not?<br> -<font color=blue>Answer</code>: The <code>MLSD</code> and <code>MLST</code> +<font color=blue>Answer</font>: The <code>MLSD</code> and <code>MLST</code> commands do not have any notions of "options" like the <code>LIST</code> and <code>NLST</code> commands do; there is no way for a client, in the request to list the files in a directory, to ask the server to filter the list of @@ -95,10 +129,10 @@ <font color=red>Question</font>: Why does <code>MLST</code> show the UIDs/GIDs for listed files, where <code>LIST</code>/<code>NLST</code> show the user/group names?<br> -<font color=blue>Answer</code>: The list of "facts" defined by RFC 3659 does +<font color=blue>Answer</font>: The list of "facts" defined by RFC 3659 does <b>not</b> include a fact for the stringified version of user/group owner names, unfortunately. This means that the <code>MLSD</code>/<code>MLST</code> -commands don't have a good way of obtaining the user/group names. +commands do not have a good way of obtaining the user/group names. <p> To work around this issue, you can add the following to your @@ -109,7 +143,31 @@ </IfModule> </pre> This tells <code>proftpd</code> to not advertise to the client that it can -support the <code>MLSD</code/<code>MLST</code> commands. +support the <code>MLSD</code>/<code>MLST</code> commands. The client will then +usually fall back to using the older <code>LIST</code> command, which +<i>does</i> include the file owner user/group names. + +<p><a name="FactsSymlinks"> +<font color=red>Question</font>: Why does FileZilla not display symlinks +properly, even though I have "ShowSymlinks on" in my <code>proftpd.conf</code>?<br> +<font color=blue>Answer</font>: Newer versions of FileZilla (and other +FTP clients) use the <code>MLSD</code> command for listing files, rather than +the older <code>LIST</code> command. And FileZilla and the +<code>mod_facts</code> disagree on the proper syntax for indicating when a +file is a symlink. + +<p> +To work around this issue, you can add the following to your +<code>proftpd.conf</code>: +<pre> + <IfModule mod_facts.c> + FactsOptions UseSlink + </IfModule> +</pre> +This tells the <code>mod_facts</code> module to use the improper +"OS.unix=slink:<i>path</i>" syntax for symlinks; this is the syntax preferred +by FileZilla (and perhaps other FTP clients). By default, the +<code>mod_facts</code> module uses the better "OS.unix=symlink" syntax. <p> <hr><br> @@ -119,7 +177,7 @@ <br><hr> <font size=2><b><i> -© Copyright 2007-2011 TJ Saunders<br> +© Copyright 2007-2012 TJ Saunders<br> All Rights Reserved<br> </i></b></font> |
