GFS_ACL_CHECK(3)

πŸ’– GFS_ACL_CHECK(3) πŸ’–

okay bestie so this is a Gfarm manual page, section 3, and it's all about gfs_acl_check β€” literally the vibe-check function for your ACLs. no cap. πŸ¦‹


✨ NAME ✨

gfs_acl_check β€” check a Gfarm ACL for validity πŸ‘‘


🌸 SYNOPSIS 🌸

#include <gfarm/gfarm.h>

gfarm_error_t gfs_acl_check(gfarm_acl_t acl, int *last_p,
                            int *acl_check_err_code_p);

like, that's the whole signature, she's not complicated, she just wants to know if your ACL is okay 🫢


πŸŽ€ INPUT ARGUMENTS πŸŽ€

  • acl β€” an ACL structure type which is sorted. yes bestie, sorted. the sort is not optional, it's the whole point. gfs_acl_sort(3) is right there in SEE ALSO for a reason πŸ’…
  • last_p β€” if this last_p is not NULL, then gfs_acl_check(3) assigns the number of the ACL entry at which the error was detected to the value pointed to by this last_p. so basically it snitches on exactly which entry was giving problems. so helpful of her honestly 😭
  • acl_check_err_code β€” this one's one of these four values:
    • GFARM_ACL_MULTI_ERROR
    • GFARM_ACL_DUPLICATE_ERROR
    • GFARM_ACL_MISS_ERROR
    • GFARM_ACL_ENTRY_ERROR

(in the synopsis she goes by acl_check_err_code_p, just so you're not confused when the names don't match up exactly β€” that's the girlies being ✨consistent✨ as always πŸ™ˆ)


⭐ RETURN VALUES ⭐

  • GFARM_ERR_NO_ERROR β€” the function terminated successfully. we love a clean run, no notes, main character energy 🌈
  • Others β€” an error except the above occurred. the reason is shown by gfarm_error_string(3), so go read that if you wanna know what went wrong, bestie πŸ”₯

🌸 SEE ALSO 🌸


πŸ’€ real talk: this is the validity check, so if your ACL is out here being messy, unsorted, duplicated, missing stuff, or just straight-up wrong at the entry level, she will find it and she will tell you exactly where. periodt.

okay that's the page!! slay πŸ’–βœ¨ this was Gfarm, from the 14 Feb 2011 era, filed under section 3, and honestly? iconic. mwah πŸŽ€πŸ¦‹πŸ’