SERVICELOG_NOTIFY(8)

πŸ“¦ version 1.1.16, in opensuse-leap 16.0

πŸ’… SERVICELOG_NOTIFY (section 8, bestie) πŸ’…

okay so real talk β€” this one's from the PowerLinux Diagnostic Tools manual, section 8, and it's genuinely so useful. it's called servicelog_notify and it's giving "personal assistant for your event log" energy. let's get into it 🫢


✨ NAME ✨

servicelog_notify β€” add, view, or remove tools to be notified when events are logged in servicelog. literally that's it, that's the job πŸ’–


🌸 SYNOPSIS 🌸

/usr/sbin/servicelog_notify --add [add_options]
/usr/sbin/servicelog_notify --remove  {--id=n | --command=cmd}
/usr/sbin/servicelog_notify --list [--id=n | --command=cmd]

like, pick your lane: add, remove, or list. can't do all three at once, that's not the vibe ✨


πŸ¦‹ DESCRIPTION πŸ¦‹

so the servicelog_notify command lets you register tools that get invoked whenever events matching the parameters you specify get logged in the servicelog. it's like setting up a little notification bestie that pings your program every time something interesting happens πŸ”₯

and because the universe believes in balance, this command also lets you list or remove those registered notification tools. add, list, remove β€” the whole lifecycle, iconique πŸ‘‘


πŸ’… OPTIONS πŸ’…

  • -l or --list β€” lists registered notification tools. by default it lists them all. if --id is specified, only the notification with that ID gets listed. if --command is specified, all notifications that execute that command get listed. slay πŸŽ€
  • -r or --remove β€” removes the notification with ID=n, if --id was specified, or removes all notifications that run the command specified by --command. bye bestie πŸ‘‹
  • -c cmd or --command=cmd β€” the command (including command-line options, so like the whole vibe) to be invoked when a matching event is logged. this is who gets the ping πŸ“£
  • -i n or --id=n β€” the ID number of the notification tool to be listed or removed. it's the little name tag 🏷️
  • -a or --add β€” creates a new notification, specified by the --match, --type, --command, and --method options. this is the main character option honestly ✨
  • -m query_string or --match=query_string β€” a filter string used to determine whether a newly-logged event should cause this notification tool to be invoked. (for example, --match='serviceable=1' to match only serviceable events.) see the "QUERY STRINGS" section in the servicelog(8) man page for more info β€” go read it, iyktyk πŸ‘€
  • --type=EVENT or --type=REPAIR or --type=EVENT|REPAIR β€” specifies whether to notify of events, or repair actions, or both. -t is a synonym for --type. choose your fighter(s) πŸ₯Š
  • --method={num_stdin|num_arg|text_stdin|pairs_stdin} β€” indicates how data should be passed to the notification tool. ok so here's the breakdown, listen up:
    • num_stdin β€” the ID of the new event gets passed to stdin.
    • num_arg β€” the ID gets passed as the last command-line argument.
    • text_stdin β€” verbose descriptive text gets passed to stdin.
    • pairs_stdin β€” data from the new event gets passed to stdin as parameter=value pairs, one per line.

and -M is a synonym for --method πŸ’«

  • -h or --help β€” display a help message and exit. the classic escape hatch πŸ™ˆ

🌈 OLD SYNTAX 🌈

okay so everything above is the command syntax accepted by v1.0 and later versions of servicelog_notify. but in v1.1, support for the following options was added for backward compatibility with v0.2.9. πŸ•°οΈ

⚠️ heads up bestie: mixing v0.2.9 options with v1.x options may produce unexpected results. like, it's not forbidden but it's giving chaos. be careful 🫢
  • --severity=sev β€” sev is a number from 1 to 7. equivalent to a severity>=sev clause in a --match query-string. πŸ”’
  • --serviceable={yes|no|all} β€” equivalent to a serviceable clause in a --match query-string (yes=1, no=0). βœ…βŒ
  • --type=event_type[|event_type...] β€” equivalent to one or more type clauses in a --match query-string. the recognized *event_type*s are:
    • os (same as $OS in a query-string)
    • ppc64_rtas ($RTAS)
    • ppc64_encl ($ENCLOSURE)
    • ppc64_bmc ($BMC)

yes those are the exact names, no i will not be shortening them πŸ’€

  • --repair_action={yes|no|all} β€” equivalent to --type=REPAIR, --type=EVENT, or --type=EVENT|REPAIR, respectively. respectively!! the order matters, remember it πŸ“
  • --query β€” same as --list, except that you must specify --id or --command. no vibing with an empty query, it needs specifics πŸ’…

πŸ‘‘ AUTHOR πŸ‘‘

written by Michael Strosaker (strosake@austin.ibm.com) and Nathan Fontenot (nfont@austin.ibm.com). v0.2.9 compatibility was added by Brad Peters and Jim Keniston (jkenisto@us.ibm.com). absolute legends, all of them πŸ«‘πŸ’–


🧚 SEE ALSO 🧚


and that's the whole page, bestie β€” go forth and get notified βœ¨πŸ’…

this masterpiece shipped on Linux, dated February 2012, and the source is the PowerLinux Diagnostic Tools manual. periodt. πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from