AUSEARCH_NEXT_EVENT(3)

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

πŸ’– NAME πŸ’–

ausearch_next_event β€” find the next event that meets search criteria πŸ‘‘

Okay bestie, so this is a <auparse.h> girly and she's the one who goes hunting through your audit stream for the next event that actually matches what you're looking for. Main character energy, truly.


✨ SYNOPSIS ✨

#include <auparse.h>

int ausearch_next_event(auparse_state_t *au);"

Like, she takes one argument (au) and she gives you back an int. That's the whole vibe. πŸŽ€


πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea πŸ“

ausearch_next_event will scan the input source and evaluate whether any record in an event contains the data being searched for. That's it, that's the job. She's out here vibe-checking your events one by one to see if any of them are giving what you asked for.

The important deets: evaluation is done at the record level. Not the event level, not the "ehhh close enough" level. Record level. Periodt. πŸ’…


πŸŽ€ RETURN VALUE πŸŽ€

She comes back with one of three numbers, and honestly it's giving traffic light:

  • -1 β€” πŸ’€ an error happened, something went wrong, not the move
  • 0 β€” 😭 no matches, nothing for you here bestie
  • 1 β€” ✨ success!! we ate, we found it πŸ”₯

🌸 SEE ALSO 🌸

Go give these sisters some love too, they're all in the same friend group:


πŸ‘‘ AUTHOR πŸ‘‘

Steve Grubb 🫢 (the icon, the legend, we stan)


and that's a wrap!! πŸ’– this little beauty comes to you from Red Hat, dating all the way back to Feb 2007 🌸 β€” the <AUSEARCH_NEXT_EVENT(3)> page itself, one of the classics. go forth and find your events, bestie πŸ¦‹βœ¨