1 files changed, 40 insertions, 0 deletions
diff --git a/docs-xml/smbdotconf/protocol/easupport.xml b/docs-xml/smbdotconf/protocol/easupport.xml
new file mode 100644
index 0000000..f111a4c
--- /dev/null
+++ b/docs-xml/smbdotconf/protocol/easupport.xml
@@ -0,0 +1,40 @@
+<samba:parameter name="ea support"
+                 context="S"
+                 type="boolean"
+                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
+<description>
+    <para>This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>                                       
+    <manvolnum>8</manvolnum></citerefentry> will allow clients to attempt to access extended
+    attributes on a share. In order to enable this parameter on a setup with default VFS modules:
+    </para>
+    <itemizedlist>
+	<listitem><para>Samba must have been built with extended attributes support.
+	</para></listitem>
+	<listitem><para>The underlying filesystem exposed by the share must support extended
+	attributes (e.g. the getfattr<manvolnum>1</manvolnum> / setfattr<manvolnum>1</manvolnum>
+	utilities must work).
+	</para></listitem>
+	<listitem><para>Access to extended user attributes must be allowed by the underlying
+        filesystem (e.g. when mounted with a system-dependent option like user_xattr on Linux).
+	</para></listitem>
+    </itemizedlist>
+    <para>
+    This option exposes the "user" attribute namespace from the underlying filesystem to
+    clients. In order to match Windows conventions, the namespace prefix ("user.") is
+    stripped from the attribute name on the client side. The handling of further attribute
+    namespaces (like "security", "system", or "trusted") is not affected by this option.
+    </para>
+    <para>
+    Note that the SMB protocol allows setting attributes whose value is 64K bytes long,
+    and that on NTFS, the maximum storage space for extended attributes per file is 64K.
+    On some filesystem the limits may be lower. Filesystems with too limited EA
+    space may experience unexpected weird effects.
+
+
+    The default has changed to yes in Samba release 4.9.0 and above to allow better Windows
+    fileserver compatibility in a default install.
+    </para>
+</description>
+
+<value type="default">yes</value>
+</samba:parameter>