SDRWATCH(1)

πŸ“¦ version 3.2.1, in ubuntu jammy

πŸ’… SDRWATCH(1) β€” bestie edition ✨

okay so we're in the ICI executables part of the manual, and today's main character is sdrwatch. buckle up πŸŽ€


🌸 NAME 🌸

sdrwatch β€” SDR non-volatile data store activity monitor πŸ‘€


✨ SYNOPSIS ✨

sdrwatch sdr_name interval count [ verbose ]

πŸ’– DESCRIPTION πŸ’–

so here's the vibe. sdrwatch is gonna do a lil loop β€” for count iterations, it sleeps for interval seconds, then calls up the sdr_print_trace() function (peep sdr(3) for the deets) to spill the tea on what SDR data storage management activity happened in the SDR data store named by sdr_name during that interval. it's giving surveillance but make it storage πŸ•΅οΈβ€β™€οΈ

and if you also pass the optional verbose parameter? the printed SDR activity trace goes verbose, exactly like it says in sdr(3). extra detail, no filter πŸ’…

lowkey the cutest part: if interval is zero, sdrwatch doesn't loop at all β€” it just prints a current usage summary for the data store you named and dips. one and done, periodt ✨

so why do you even care? because sdrwatch is so helpful for detecting and diagnosing storage space leaks 🚨 storage leaks are the worst, they just keep eating and never stop, not cute.

and for debugging the ION protocol stack specifically, sdr_name is normally "ion" β€” but heads up bestie, it might get overridden by the value of sdrName in the .ionconfig file used to configure the node under study. so check your config before you assume, iykyk πŸ¦‹


🫢 EXIT STATUS 🫢

  • "0" β€” sdrwatch has terminated. that's it, that's the whole list. it said its piece and left πŸ‘‘

πŸŽ€ FILES πŸŽ€

No configuration files are needed. none. zero. we love a low-maintenance icon πŸ’–


🌈 ENVIRONMENT 🌈

No environment variables apply. nothing to export, nothing to source, we're chilling 🧚


πŸ’€ DIAGNOSTICS πŸ’€

if things go sideways, these diagnostics may be issued to the ion.log log file:

  • Can't attach to sdr. β€” this is an ION system error 😭 one possible cause is that ION hasn't been initialized on the local computer yet. run ionadmin(1) to correct it, easy fix bestie.
  • Can't start trace. β€” not enough ION working memory to contain the trace information πŸ™ˆ reinitialize ION with more memory.

πŸ› BUGS πŸ›

found a bug? report it to <ion-bugs@korgano.eecs.ohiou.edu> β€” they wanna know fr fr πŸ“¬


⭐ SEE ALSO ⭐


okay that's the whole page, you ate that πŸ’… this was SDRWATCH(1) from the ICI executables, perl v5.24.1, dated 2016-07-07 β€” mwah, go leak-hunt responsibly, ily 🫢✨🌸

πŸ“¦ where this page comes from