From 21794b0dd28a80b149342b3218d7ebb4c8791e09 Mon Sep 17 00:00:00 2001
From: Volker Lendecke <vl@samba.org>
Date: Tue, 29 Sep 2009 14:34:16 +0200
Subject: s3: Document the "share:fake_fscaps" parameter, fix bug 6765

---
 docs-xml/smbdotconf/protocol/sharefakefscaps.xml | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 docs-xml/smbdotconf/protocol/sharefakefscaps.xml

(limited to 'docs-xml/smbdotconf/protocol')

diff --git a/docs-xml/smbdotconf/protocol/sharefakefscaps.xml b/docs-xml/smbdotconf/protocol/sharefakefscaps.xml
new file mode 100644
index 0000000000..713b95bda7
--- /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>
-- 
cgit