HP CIFS Server 2.2i Administrator's Guide version A.01.11.01

Managing HP-UX File Access Permissions from Windows NT/XP/2000
Configuring Samba ACL Support
Chapter 3 81
If a Windows client makes a request to see the ACL for a file on an HFS
file system in that share, Samba attempts to use the POSIX ACL system
call. It will fail and return an error indicating that the ACL scheme is not
supported on that file. Then Samba would try the HFS ACL system call
and it would succeed. The user would not see the initial failure described
in this example.
Example 2:
acl schemes = unix
This is the default ACL scheme. The default ignores UNIX ACL
capabilities and uses UNIX file permissions, as was the case with
previous versions of Samba.
Example 3:
acl schemes = none
This ACL example turns off all ACL support for the share and causes an
error to be returned whenever a client tries to get or to set ACL
information on any file system on the share.
Example 4:
acl schemes = hpux_posix
This ACL example supports only VxFS POSIX ACLs on the entire share.
For files on NFS, HFS or VxFS pre 3.3 file systems, all attempts from the
client to get or to set ACLs will fail. This example will not fall back to the
UNIX file permissions. ACL support will only work for files on file
systems supporting POSIX ACLs (currently VxFS 3.3 or higher).
Example 5:
acl schemes = unix hpux_posix
This ACL example is the same as setting acl scheme to unix (Example 2)
because UNIX file permissions are supported on every UNIX file system
type. This means the scheme will never fall through to the next ACL
scheme in the list. The unix scheme will be the first and last scheme
attempted in each case.
The examples described above show how any combination of ACL
schemes can be supported on a Samba share.
If you plan to have many schemes in the ACL scheme list, you will want
to setup the best order to maximize efficiency. For example, if the files
accessed the most are all on a VxFS 3.3 file system, put hpux_posix first