ACL_DELETE(3)

📦 version 15.1, in freebsd 14.5, freebsd 15.1

🎀 ACL_DELETE(3) 🎀

Okay so this is the Library Functions Manual page for ACL_DELETE(3), and it's literally all about deleting ACLs from files. Bestie, grab your strawberry emoji 🍓 and let's go.

🌸 NAME 🌸

acl_delete_def_file, acl_delete_def_link_np, acl_delete_fd_np, acl_delete_file_np, acl_delete_link_np — delete an ACL from a file

📚 LIBRARY 📚

It's the Standard C Library (libc, -lc). Slay.

✨ SYNOPSIS ✨

#include <sys/types.h>
#include <sys/acl.h>

int
acl_delete_def_file(const char *path_p);

int
acl_delete_def_link_np(const char *path_p);

int
acl_delete_fd_np(int filedes, acl_type_t type);

int
acl_delete_file_np(const char *path_p, acl_type_t type);

int
acl_delete_link_np(const char *path_p, acl_type_t type);

💅 DESCRIPTION 💅

Okay so the whole squad — acl_delete_def_file(), acl_delete_def_link_np(), acl_delete_fd_np(), acl_delete_file_np(), and acl_delete_link_np() — each allow the deletion of an ACL from a file.

The acl_delete_def_file() function is a POSIX.1e call that deletes the default ACL from a file (normally a directory) by name. Iconic. The remainder of the calls are non-portable extensions that permit the deletion of arbitrary ACL types from a file/directory either by path name or file descriptor.

And here's the symlink tea ☕: the _file() variations follow a symlink if it occurs in the last segment of the path name; the _link() variations operate on the symlink itself. Periodt.

🧚 IMPLEMENTATION NOTES 🧚

Heads up bestie: FreeBSD's support for POSIX.1e interfaces and features is still under development at this time. It's giving "work in progress," not "finished era." 🫶

🦋 RETURN VALUES 🦋

Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error.

🔥 ERRORS 🔥

If any of the following conditions occur, these functions shall return -1 and set errno to the corresponding value:

  • [EACCES] — Search permission is denied for a component of the path prefix, or the object exists and the process does not have appropriate access rights.
  • [EBADF] — The fd argument is not a valid file descriptor.
  • [EINVAL] — The ACL type passed is invalid for this file object.
  • [ENAMETOOLONG] — A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
  • [ENOENT] — The named object does not exist, or the path_p argument points to an empty string.
  • [ENOMEM] — Insufficient memory available to fulfill request.
  • [ENOTDIR] — A component of the path prefix is not a directory.
    • Also: Argument path_p must be a directory, and is not. Like, it's literally not giving directory energy 😭
  • [EOPNOTSUPP] — The file system does not support ACL deletion.
  • [EPERM] — The process does not have appropriate privilege to perform the operation to delete an ACL.
  • [EROFS] — The file system is read-only.

🌈 SEE ALSO 🌈

👑 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 information.

⭐ HISTORY ⭐

POSIX.1e support was introduced in FreeBSD 4.0, and development continues.

💜 AUTHORS 💜

Robert N M Watson

🫶 Cute sign-off: source/version is Debian, and the date on this page is December 29, 2002. Bye bestie, go delete those ACLs responsibly 💖
📦 where this page comes from