HP Surestore NAS - Manual (Page 65)

65
This table shows the mapping that takes place between the permissions.
UNIX NT Equivalent
r-- Read
-w- Write, Delete
--x Execute
-wx Write, Delete, Execute
r-x Read, Execute
rw- Read, Write, Delete
rwx Full Access
--- No Access
Note: If share-level security is being used in the Windows environment, then only the share
passwords affect access. The UNIX permissions have no effect.
Accessing Files Created by NT Clients
Directly mapping NT permissions to UNIX permissions causes some difficulty because NT
permissions have a greater level of complexity. UNIX users are unable to use either the chmod or
chown commands to modify the permissions or owners of NT files. The table below shows which
UNIX-to-NT file permissions are mapped.
NT UNIX
R r
W w
X x
D Ignored
P Denied
O Denied
In addition to the permission mappings covered in the previous sections, the following also
applies:
o If no ACLs are specified, then the UNIX permission will be rwxrwxrwx.
o If the ACL is empty, then the UNIX permissions will be ---------.
o If the only access allowed by the ACL grants full control to everyone, then the UNIX
permissions will be rwxrwxrwx.
o In the absence of a group ACL, the owning group will be the user's primary group
and the group permissions are set to the same value as the other permissions.
Additionally, if an NT file grants permission to the everyone group (and does not specifically deny
access to the owner or the group), then the same access is given to the owner and the primary
group. However, UNIX permissions look for explicit permissions for the owner, group, and other.
To allow the same level of access in UNIX as NT, these files will have a permission of r--r--r--.
CIFS file locking
To ensure integrity and security of user data files despite the variable client access methods, file
locking can be enabled at the file system and/or application level.