ACL_FROM_TEXT(3) BSD Library Functions Manual ACL_FROM_TEXT(3)NAMEacl_from_text — create an ACL from text
Standard C Library (libc, -lc)
acl_from_text(const char *buf_p);
The acl_from_text() function converts the text form of an ACL referred to
by buf_p into the internal working structure for ACLs, appropriate for
applying to files or manipulating.
This function may cause memory to be allocated. The caller should free
any releasable memory, when the new ACL is no longer required, by calling
acl_free(3) with the (void *)acl_t as an argument.
FreeBSD'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
internal representation of the ACL in working storage. Otherwise, a
value of (acl_t)NULL shall be returned, and errno shall be set to indi‐
cate the error.
If any of the following conditions occur, the acl_from_text() function
shall return a value of (acl_t)NULL and set errno to the corresponding
[EINVAL] Argument buf_p cannot be translated into an ACL.
[ENOMEM] The ACL working storage requires more memory than is
allowed by the hardware or system-imposed memory man‐
SEE ALSOacl(3), acl_free(3), acl_get(3), acl_to_text(3), posix1e(3)STANDARDS
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 FreeBSD POSIX.1e implementation page for more
POSIX.1e support was introduced in FreeBSD 4.0, and development contin‐
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.
BSD January 28, 2000 BSD