AUPARSE_NODE_COMPARE(3)

πŸ“¦
version 4.2.1 Β· 3 versions
, in alpine 3.23, alpine 3.24, arch rolling, centos-stream 10, fedora 43, fedora 44, nixpkgs unstable, ubuntu resolute, ubuntu stonking

πŸ’– AUPARSE_NODE_COMPARE(3) πŸ’–

okay bestie, welcome to the Linux Audit API corner of the group chat 🫢 this one's called auparse_node_compare and she's a whole lil function, no cap.


✨ NAME ✨

auparse_node_compare β€” literally just compares node name values πŸ’…


🌸 SYNOPSIS 🌸

#include <auparse.h>

int auparse_node_compare(const au_event_t *e1,constau_event_t*"e2);"

πŸ¦‹ DESCRIPTION πŸ¦‹

so the way that auparse_node_compare works is: it takes the node name values from 2 events and compares them. that's it. that's the whole vibe check. two events walk in, their node names get held up next to each other, and the function tells you how they stack up. iconic behavior honestly 🌈


πŸ‘‘ RETURN VALUE πŸ‘‘

she hands back -1, 0, or 1, depending on whether e2 is less than, equal to, or greater than e1 β€” respectively. in that order. don't mix it up πŸ™ˆ

and since this is a string compare, it probably only matters whether they're equal or not equal. the less-than/greater-than thing is lowkey just along for the ride. periodt πŸ’€

ngl bestie, remember it's e2 being judged against e1, not the other way around. the order is the whole plot twist here.

πŸ”₯ SEE ALSO πŸ”₯


⭐ AUTHOR ⭐

Steve Grubb β€” the main character who wrote this βœ¨πŸ‘‘


and that's the page, bestie!! this lil slice of the Linux Audit API is brought to you by Red Hat, dated Sept 2007 πŸ“ like... a vintage queen fr fr. go forth and compare those node names, you've got this πŸ’œπŸ§š