29.01.2013 Views

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

GPFS: Administration and Programming Reference - IRA Home

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

mmputacl Comm<strong>and</strong><br />

Name<br />

mmputacl – Sets the <strong>GPFS</strong> access control list for the specified file or directory.<br />

Synopsis<br />

mmputacl [-d] [-i InFilename] Filename<br />

Description<br />

Use the mmputacl comm<strong>and</strong> to set the ACL of a file or directory.<br />

If the -i option is not used, the comm<strong>and</strong> expects the input to be supplied through st<strong>and</strong>ard input, <strong>and</strong><br />

waits for your response to the prompt.<br />

For information about NFS V4 ACLs, see Chapter 6, “Managing <strong>GPFS</strong> access control lists <strong>and</strong> NFS<br />

export,” on page 45.<br />

Any output from the mmgetacl comm<strong>and</strong> can be used as input to mmputacl. The comm<strong>and</strong> is extended<br />

to support NFS V4 ACLs. In the case of NFS V4 ACLs, there is no concept of a default ACL. Instead,<br />

there is a single ACL <strong>and</strong> the individual access control entries can be flagged as being inherited (either by<br />

files, directories, both, or neither). Consequently, specifying the -d flag for an NFS V4 ACL is an error. By<br />

its nature, storing an NFS V4 ACL implies changing the inheritable entries (the <strong>GPFS</strong> default ACL) as well.<br />

Table 8 describes how mmputacl works.<br />

Table 8. The mmputacl comm<strong>and</strong> for POSIX <strong>and</strong> NFS V4 ACLs<br />

Comm<strong>and</strong> POSIX ACL NFS V4 ACL<br />

mmputacl Access ACL (Error if default ACL is NFS V4 [1]) Stores the ACL (implies default as well)<br />

mmputacl -d Default ACL (Error if access ACL is NFS V4 [1]) Error: NFS V4 ACL (has no default ACL)<br />

[1] The default <strong>and</strong> access ACLs are not permitted to be mixed types because NFS V4 ACLs include inherited<br />

entries, which are the equivalent of a default ACL. An mmdelacl of the NFS V4 ACL is required before an ACL is<br />

converted back to POSIX.<br />

Depending on the file system’s -k setting (posix, nfs4, or all), mmputacl may be restricted. The<br />

mmputacl comm<strong>and</strong> is not allowed to store an NFS V4 ACL if -k posix is in effect. The mmputacl<br />

comm<strong>and</strong> is not allowed to store a POSIX ACL if -k nfs4 is in effect. For more information, see the<br />

description of the -k flag for the mmchfs, mmcrfs, <strong>and</strong> mmlsfs comm<strong>and</strong>s.<br />

Note that the test to see if the given ACL is acceptable based on the file system’s -k setting cannot be<br />

done until after the ACL is provided. For example, if mmputacl file1 is issued (no -i flag specified) the<br />

user then has to input the ACL before the comm<strong>and</strong> can verify that it is an appropriate ACL given the file<br />

system settings. Likewise, the comm<strong>and</strong> mmputacl -d dir1 (again the ACL was not given with the -i flag)<br />

requires that the ACL be entered before file system ACL settings can be tested. In this situation, the -i flag<br />

may be preferable to manually entering a long ACL, only to find out it is not allowed by the file system.<br />

Parameters<br />

Filename<br />

The path name of the file or directory for which the ACL is to be set. If the -d option is specified,<br />

Filename must be the name of a directory.<br />

Chapter 8. <strong>GPFS</strong> comm<strong>and</strong>s 233

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!