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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

mmgetacl Comm<strong>and</strong><br />

Parameters<br />

Filename<br />

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

specified, Filename must contain the name of a directory.<br />

Options<br />

-d Specifies that the default ACL of a directory is to be displayed.<br />

-k {nfs4 | posix | native}<br />

nfs4 Always produces an NFS V4 ACL.<br />

posix Always produces a traditional ACL.<br />

native Always shows the ACL in its true form regardless of the file system setting.<br />

-o OutFilename<br />

The path name of a file to which the ACL is to be written.<br />

Exit status<br />

0 Successful completion.<br />

nonzero A failure has occurred.<br />

Security<br />

You must have read access to the directory where the file exists to run the mmgetacl comm<strong>and</strong>.<br />

You may issue the mmgetacl comm<strong>and</strong> only from a node in the <strong>GPFS</strong> cluster where the file system is<br />

mounted.<br />

Examples<br />

1. To display the ACL for a file named project2.history, issue this comm<strong>and</strong>:<br />

mmgetacl project2.history<br />

The system displays information similar to:<br />

#owner:paul<br />

#group:design<br />

user::rwxc<br />

group::r-x-<br />

other::r-x-<br />

2. This is an example of an NFS V4 ACL displayed using mmgetacl. Each entry consists of three lines<br />

reflecting the greater number of permissions in a text format. An entry is either an allow entry or a<br />

deny entry. An X indicates that the particular permission is selected, a minus sign (–) indicates that is<br />

it not selected. The following access control entry explicitly allows READ, EXECUTE <strong>and</strong> READ_ATTR<br />

to the staff group on a file:<br />

group:staff:r-x-:allow<br />

(X)READ/LIST (-)WRITE/CREATE (-)MKDIR (-)SYNCHRONIZE (-)READ_ACL (X)READ_ATTR (-)READ_NAMED<br />

(-)DELETE (-)DELETE_CHILD (-)CHOWN (X)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED<br />

3. This is an example of a directory ACLs, which may include inherit entries (the equivalent of a default<br />

ACL). These do not apply to the directory itself, but instead become the initial ACL for any objects<br />

created within the directory. The following access control entry explicitly denies READ/LIST,<br />

READ_ATTR, <strong>and</strong> EXEC/SEARCH to the sys group.<br />

group:sys:----:deny:DirInherit<br />

(X)READ/LIST (-)WRITE/CREATE (-)MKDIR (-)SYNCHRONIZE (-)READ_ACL (X)READ_ATTR (-)READ_NAMED<br />

(-)DELETE (-)DELETE_CHILD (-)CHOWN (X)EXEC/SEARCH (-)WRITE_ACL (-)WRITE_ATTR (-)WRITE_NAMED<br />

186 <strong>GPFS</strong>: <strong>Administration</strong> <strong>and</strong> <strong>Programming</strong> <strong>Reference</strong>

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

Saved successfully!

Ooh no, something went wrong!