s3: Document the "share:fake_fscaps" parameter, fix bug 6765

(cherry picked from commit 21794b0dd28a80b149342b3218d7ebb4c8791e09)
(cherry picked from commit d046ab32094caa9511862144df1c00e64c234487)

diff --git a/docs-xml/smbdotconf/protocol/sharefakefscaps.xml b/docs-xml/smbdotconf/protocol/sharefakefscaps.xml
new file mode 100644 (file)
index 0000000..713b95b
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/sharefakefscaps.xml
@@ -0,0 +1,20 @@
+<samba:parameter name="share:fake_fscaps"
+       context="G"
+       type="string"
+                advanced="1" developer="0"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+
+       <para>
+       This is needed to support some special application that makes
+       QFSINFO calls to check whether we set the SPARSE_FILES bit
+       (0x40). If this bit is not set that particular application
+       refuses to work against
+       Samba. With <smbconfoption name="share:fake_fscaps">64</smbconfoption>
+       the SPARSE_FILES file system capability flag is set. Use other
+       decimal values to specify the bitmask you need to fake.
+       </para>
+
+</description>
+<value type="default">0</value>
+</samba:parameter>