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.

Table 5 describes how mmeditacl works.<br />

Table 5. The mmeditacl comm<strong>and</strong> for POSIX <strong>and</strong> NFS V4 ACLs<br />

Comm<strong>and</strong> ACL mmcrfs -k Display -d (default)<br />

mmeditacl posix posix Access ACL Default ACL<br />

mmeditacl posix nfs4 NFS V4 ACL Error[1]<br />

mmeditacl posix all Access ACL Default ACL<br />

mmeditacl nfs4 posix Access ACL[2] Default ACL[2]<br />

mmeditacl nfs4 nfs4 NFS V4 ACL Error[1]<br />

mmeditacl nfs4 all NFS V4 ACL Error[1]<br />

mmeditacl -k native posix any Access ACL Default ACL<br />

mmeditacl -k native nfs4 any NFS V4 ACL Error[1]<br />

mmeditacl -k posix posix any Access ACL Default ACL<br />

mmeditacl -k posix nfs4 any Access ACL[2] Default ACL[2]<br />

mmeditacl -k nfs4 any any NFS V4 ACL Error[1]<br />

[1] NFS V4 ACLs include inherited entries. Consequently, there cannot be a separate default ACL.<br />

[2] Only the mode entries (owner, group, everyone) are translated. The rwx values are derived from the NFS V4 file<br />

mode attribute. Since the NFS V4 ACL is more granular in nature, some information is lost in this translation.<br />

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

individual access control entries can be flagged as being inherited (either by files, directories, both, or<br />

neither). Consequently, specifying the -d flag for an NFS V4 ACL is an error. By its nature, storing an NFS<br />

V4 ACL implies changing the inheritable entries (the <strong>GPFS</strong> default ACL) as well.<br />

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

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

store a POSIX ACL if -k nfs4 is in effect. For more information, see the description of the -k flag for the<br />

mmchfs, mmcrfs, <strong>and</strong> mmlsfs comm<strong>and</strong>s.<br />

Parameters<br />

Filename<br />

The path name of the file or directory for which the ACL is to be edited. 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 edited.<br />

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

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

posix Always produces a traditional ACL.<br />

mmeditacl Comm<strong>and</strong><br />

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

This option should not be used for routine ACL manipulation. It is intended to provide a way to<br />

show the translations that are done. For example, if a posix ACL is translated by NFS V4. Beware<br />

that if the -k nfs4 flag is used, but the file system does not allow NFS V4 ACLs, you will not be<br />

able to store the ACL that is returned. If the file system does support NFS V4 ACLs, the -k nfs4<br />

flag is an easy way to convert an existing posix ACL to nfs4 format.<br />

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

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

Saved successfully!

Ooh no, something went wrong!