Note how vfs_gpfs uses the "acl map full control" parameter.

Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: Ira Cooper <ira@samba.org>
Autobuild-User(master): Jeremy Allison <jra@samba.org>
Autobuild-Date(master): Mon Jun 24 21:24:38 CEST 2013 on sn-devel-104

diff --git a/docs-xml/manpages/vfs_gpfs.8.xml b/docs-xml/manpages/vfs_gpfs.8.xml
index 7f560ca23a49ded2dbeac69f03911fa7d513b043..d1243a9b10f03f00488fcb1ddc6b4f175c9f12a4 100644 (file)
--- a/docs-xml/manpages/vfs_gpfs.8.xml
+++ b/docs-xml/manpages/vfs_gpfs.8.xml
@@ -48,6 +48,16 @@
        are the responsibility of the underlying filesystem than of Samba.
        </para>
 
+       <para>This module makes use of the smb.conf parameter
+       <smbconfoption name="acl map full control">acl map full control</smbconfoption>
+       When set to yes (the default), this parameter will add in the FILE_DELETE_CHILD
+       bit on a returned ACE entry for a file (not a directory) that already
+       contains all file permissions except for FILE_DELETE and FILE_DELETE_CHILD.
+       This can prevent Windows applications that request GENERIC_ALL access
+       from getting ACCESS_DENIED errors when running against a filesystem
+       with NFSv4 compatible ACLs.
+       </para>
+
        <para>This module is stackable.</para>
 
        <para>Since Samba 4.0 all options are per share options.</para>