sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-11 05:18:09 +03:00
Code

doc: update "ea support" section of the smb.conf manpage

Browse Source 
This section was badly outdated.

Signed-off-by: Uri Simchoni <uri@samba.org>
Reviewed-by: Ralph Boehme <slow@samba.org>

Autobuild-User(master): Ralph Böhme <slow@samba.org>
Autobuild-Date(master): Sun Mar 12 21:04:11 CET 2017 on sn-devel-144
This commit is contained in:
Uri Simchoni 2017-03-03 22:00:00 +02:00 committed by Ralph Boehme
parent 9eb46d587a
commit 65aafb14b7
1 changed files with 21 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs-xml/smbdotconf/protocol/easupport.xml
View File

@ -4,12 +4,27 @@
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 store OS/2 style Extended
attributes on a share. In order to enable this parameter the underlying filesystem exported by
the share must support extended attributes (such as provided on XFS and EXT3 on Linux, with the
correct kernel patches). On Linux the filesystem must have been mounted with the mount
option user_xattr in order for extended attributes to work, also
extended attributes must be compiled into the Linux kernel.</para>
<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>
</itemizedlist>
<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 most UNIX systems (Solaris and ZFS file system being the exception), the limits
are much lower - typically 4K. Worse, the same 4K space is often used to store
system metadata such as POSIX ACLs, or Samba's NT ACLs. Giving clients
access to this tight space via extended attribute support could consume all
of it by unsuspecting client applications, which would prevent changing
system metadata due to lack of space.
</para>
</description>
<value type="default">no</value>