PSMWATCH(1)
π PSMWATCH(1) β bestie edition π
ok so like, this is psmwatch from the ICI executables era, and it's literally the PSM memory partition activity monitor. yes the manual is PSMWATCH(1). we're doing this. π«Ά
β¨ NAME β¨
psmwatch β PSM memory partition activity monitor. that's it, that's the whole vibe. it watches. it monitors. it's giving surveillance but for memory. π
πΈ SYNOPSIS πΈ
psmwatch shared_memory_key memory_size partition_name interval count [ verbose ]
π¦ DESCRIPTION π¦
okay bestie, here's the tea. for count iterations, psmwatch sleeps for interval seconds and then invokes the psm_print_trace() function (peep psm(3) for the lore) to report on all the PSM dynamic memory management activity happening in the PSM-managed shared memory partition that's identified by shared_memory_key during that interval. it's like a little memory gossip session. π
if you also pass the optional verbose parameter, then the printed PSM activity trace gets verbose, exactly as described in psm(3). no cap.
now, to prevent confusion (because confusion is NOT the vibe), the memory_size and partition_name you specify get compared against the ones that were declared when this shared memory partition was first managed. if they don't match? psmwatch immediately terminates. like, instantly. no hesitation, no explanation, just gone. π
if interval is zero, then psmwatch doesn't loop at all β it merely prints a current usage summary for the indicated shared-memory partition and then terminates. quick lil check-in. β¨
psmwatch is super helpful for detecting and diagnosing memory leaks. and fr fr, for debugging the ION protocol stack, here's what each parameter should be:
shared_memory_keyβ normally"65281", but it might get overridden by the value ofwmKeyin the.ionconfigfile that was used to configure the node under study. iykyk.memory_sizeβ as given by the value ofwmKeyin the.ionconfigfile used to configure the node under study. and if that value isn't stated in the.ionconfigfile, the default is"5000000". remember that number, bestie. πpartition_nameβ always"ionwm". always. every single time. periodt. π
π EXIT STATUS π
"0"βpsmwatchhas terminated. bye bestie, it's done, it's over, it slayed. π
π FILES π
No configuration files are needed. none. zero. we're low maintenance and unbothered. π§
π ENVIRONMENT π
No environment variables apply. she doesn't read the room, she doesn't read the env. π
π₯ DIAGNOSTICS π₯
the following diagnostics may be issued to the ion.log log file β so check there if things get dramatic:
- Can't attach to psm. β this is an ION system error. one possible cause is that ION has not yet been initialized on the local computer. run
ionadmin(1)to correct this. like, go do it. right now. π«Ά - Can't start trace. β insufficient ION working memory to contain trace information. reinitialize ION with more memory. she's hungry, feed her. π
π BUGS π
Report bugs to <ion-bugs@korgano.eecs.ohiou.edu>. tell them everything, they can handle it. π
β SEE ALSO β
and that's the whole page bestie!! this one was rendered by perl v5.24.1 back on 2016-07-07, which is honestly ancient history in group-chat years, but the knowledge still hits. go monitor some memory. ily. πβ¨π¦
π¦ where this page comes from
- ubuntu jammy: ion 3.2.1+dfsg-1.1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms