AUPARSE_FIND_FIELD_NEXT(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_FIND_FIELD_NEXT πŸ’–

okay bestie, so this one lives in the Linux Audit API corner of section 3 of the manual, and it's called auparse_find_field_next β€” say that three times fast, I dare you 🫢


✨ NAME ✨

auparse_find_field_next β€” find next occurrence of field name πŸ‘‘


🌸 SYNOPSIS 🌸

#include <auparse.h>

const char * auparse_find_field_next(const auparse_state_t *au);"

(yes the quote at the end is just... there. iconic of it, honestly πŸ’…)


πŸ¦‹ DESCRIPTION πŸ¦‹

so auparse_find_field_next goes looking for the next occurrence of the field name that was previously stored. not a new field name, bestie β€” the one you already had in your back pocket. it keeps scanning and scanning until it hits the last record of the current event, and then it's like "okay that's the whole event, bye" πŸŽ€

think of it as the sequel to auparse_find_field β€” same vibe, next chapter, main character energy πŸ”₯


⭐ RETURN VALUE ⭐

  • it returns NULL if the field is not found 😭 (the audacity)
  • if an error happens, errno gets set. so check it, fr fr πŸ™ˆ
  • otherwise? it hands you a pointer to the text value associated with the field. slay ✨

🌈 SEE ALSO 🌈

go read those too, they're the whole friend group πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

Steve Grubb πŸ’–


and that's the whole page, bestie!! this little gem came from <strong>Red Hat</strong>, and the date on it is <strong>Feb 2007</strong> β€” vintage, retro, lowkey a classic πŸŽ€ go forth and find those fields, you got this 🌸✨πŸ’