| ACL_TEXT_VERBOSE Format ACL using verbose form
ACL_TEXT_NUMERIC_IDS Do not resolve IDs into user or group names
ACL_TEXT_APPEND_ID In addition to user and group names, append numeric IDs
This function allocates any memory necessary to contain the string and returns a pointer to the string. The caller should free any releasable memory, when the new string is no longer required, by calling acl_free(3) with the (void*)char as an argument.
.Fx Ns s support for POSIX.1e interfaces and features is still under development at this time.
Upon successful completion, the function shall return a pointer to the long text form of an ACL. Otherwise, a value of (char*)NULL shall be returned and errno shall be set to indicate the error.
If any of the following conditions occur, the acl_to_text function shall return a value of (acl_t)NULL and set errno to the corresponding value:
[EINVAL] Argument acl does not point to a valid ACL.
The ACL denoted by acl contains one or more improperly formed ACL entries, or for some other reason cannot be translated into a text form of an ACL.
[ENOMEM] The character string to be returned requires more memory than is allowed by the hardware or software-imposed memory management constraints.
acl(3), acl_free(3), acl_from_text(3), posix1e(3)
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion of the draft continues on the cross-platform POSIX.1e implementation mailing list. To join this list, see the
.Fx POSIX.1e implementation page for more information.
POSIX.1e support was introduced in
.Fx 4.0 , and development continues.
.An Robert N M Watson
The acl_from_text and acl_to_text functions rely on the getpwent(3) library calls to manage username and uid mapping, as well as the getgrent(3) library calls to manage groupname and gid mapping. These calls are not thread safe, and so transitively, neither are acl_from_text and acl_to_text. These functions may also interfere with stateful calls associated with the getpwent and getgrent calls.