• R/O
  • SSH
  • HTTPS

samba-jp: 提交


Commit MetaInfo

修訂3047 (tree)
時間2017-11-30 17:03:29
作者matsuand

Log Message

Update document formatting.

Change Summary

差異

--- trunk/docs-xml/smbdotconf/protocol/easupport.xml (revision 3046)
+++ trunk/docs-xml/smbdotconf/protocol/easupport.xml (revision 3047)
@@ -3,6 +3,12 @@
33 type="boolean"
44 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
55 <description>
6+<!-- 原文 samba-4.7.0
7+ <para>This boolean parameter controls whether <citerefentry><refentrytitle>smbd</refentrytitle>
8+ <manvolnum>8</manvolnum></citerefentry> will allow clients to attempt to access extended
9+ attributes on a share. In order to enable this parameter on a setup with default VFS modules:
10+ </para>
11+-->
612 <para> この真偽値パラメーターにより、
713 <citerefentry><refentrytitle>smbd</refentrytitle><manvolnum>8</manvolnum></citerefentry>
814 は、クライアントが共有内に OS/2 形式の拡張属性を格納することを可能とする。
@@ -10,6 +16,46 @@
1016 (Linux の場合 XFS や EXT3 に対するパッチとして提供されているような) 拡張属性をサポートしていることが必要である。
1117 Linux の場合、拡張属性を有効にするには、カーネルが拡張属性を有効にしてコンパイルされていることに加え、
1218 ファイルシステムのマウントオプションとして user_xattr を指定してマウントする必要がある。</para>
19+<!-- 原文 samba-4.7.0
20+ <itemizedlist>
21+ <listitem><para>Samba must have been built with extended attributes support.
22+ </para></listitem>
23+ <listitem><para>The underlying filesystem exposed by the share must support extended
24+ attributes (e.g. the getfattr<manvolnum>1</manvolnum> / setfattr<manvolnum>1</manvolnum>
25+ utilities must work).
26+ </para></listitem>
27+ </itemizedlist>
28+-->
29+ <itemizedlist>
30+ <listitem><para>Samba must have been built with extended attributes support.
31+ </para></listitem>
32+ <listitem><para>The underlying filesystem exposed by the share must support extended
33+ attributes (e.g. the getfattr<manvolnum>1</manvolnum> / setfattr<manvolnum>1</manvolnum>
34+ utilities must work).
35+ </para></listitem>
36+ </itemizedlist>
37+<!-- 原文 samba-4.7.0
38+ <para>
39+ Note that the SMB protocol allows setting attributes whose value is 64K bytes long,
40+ and that on NTFS, the maximum storage space for extended attributes per file is 64K.
41+ On most UNIX systems (Solaris and ZFS file system being the exception), the limits
42+ are much lower - typically 4K. Worse, the same 4K space is often used to store
43+ system metadata such as POSIX ACLs, or Samba's NT ACLs. Giving clients
44+ access to this tight space via extended attribute support could consume all
45+ of it by unsuspecting client applications, which would prevent changing
46+ system metadata due to lack of space.
47+ </para>
48+-->
49+ <para>
50+ Note that the SMB protocol allows setting attributes whose value is 64K bytes long,
51+ and that on NTFS, the maximum storage space for extended attributes per file is 64K.
52+ On most UNIX systems (Solaris and ZFS file system being the exception), the limits
53+ are much lower - typically 4K. Worse, the same 4K space is often used to store
54+ system metadata such as POSIX ACLs, or Samba's NT ACLs. Giving clients
55+ access to this tight space via extended attribute support could consume all
56+ of it by unsuspecting client applications, which would prevent changing
57+ system metadata due to lack of space.
58+ </para>
1359 </description>
1460 <value type="default">no</value>
1561 </samba:parameter>
Show on old repository browser