.\" NFSv4 Access Control Lists manual pages
.\" format with: groff -man -Tascii foo.1
.\" 
.\" http://www.delorie.com/gnu/docs/groff/groff_37.html
.\" http://www.schweikhardt.net/man_page_howto.html
.\" 
.TH NFS4_GETFACL 1 "version 0.3.4, August 2018" "Linux" "NFSv4 Access Control Lists"
.SH NAME
nfs4_getfacl \- get NFSv4 file/directory access control lists
.SH SYNOPSIS
.B nfs4_getfacl [-HR]
file ...
.SH DESCRIPTION
.B nfs4_getfacl 
will display the NFSv4 Access Control List (ACL) for the files given
as arguments, provided they are on mounted NFSv4 filesystems which
support ACLs.

If the 
.BR -H / --more-help
flag is specified,
.B nfs4_getfacl
will print some information about NFSv4 ACLs and the fields used in ACEs.

If the
.BR -R / --recursive
flag is specified, 
.B nfs4_getfacl
will list the NFSv4 ACLs of all files and directories recursively.

If the
.BR -c / --omit-header
flag is specified,
.B nfs4_getfacl
will not display the comment header (Do not print filename).

The output format for an NFSv4 file ACL, e.g., is:
.RS
.nf

# file: /somedir
A::OWNER@:rwatTnNcCy
A::alice@nfsdomain.org:rxtncy
A::bob@nfsdomain.org:rwadtTnNcCy
A:g:GROUP@:rtncy
D:g:GROUP@:waxTC
A::EVERYONE@:rtncy
D::EVERYONE@:waxTC
.fi
.RE

In the example output above, the user `alice@nfsdomain.org' has the equivalent
of "read" and "execute" permissions, `bob@nfsdomain.org' has "read" and 
"write", and both `GROUP@' and `EVERYONE@' have "read".

The ACL listings of multiple files are separated by blank lines.

Refer to the 
.BR nfs4_acl (5)
manpage for detailed information about NFSv4 ACL terminology and syntax. 
.SH AUTHORS
.B nfs4_getfacl
was written by people at CITI, the Center for Information Technology Integration
.RI ( http://www.citi.umich.edu ).
This manpage was written by David Richter.
.SH CONTACT
Please send bug reports, feature requests, and comments to
.RI < linux-nfs@vger.kernel.org >.
.SH SEE ALSO
.BR nfs4_setfacl "(1), " nfs4_acl (5),
.IR RFC3530 " (NFSv4.0), NFSv4.1 Minor Version Draft."