Provided by: ion_3.2.1+dfsg-1.1_amd64
psmwatch - PSM memory partition activity monitor
psmwatch shared_memory_key memory_size partition_name interval count [ verbose ]
For count interations, psmwatch sleeps interval seconds and then invokes the psm_print_trace() function (see psm(3)) to report on PSM dynamic memory management activity in the PSM-managed shared memory partition identified by shared_memory_key during that interval. If the optional verbose parameter is specified, the printed PSM activity trace will be verbose as described in psm(3). To prevent confusion, the specified memory_size and partition_name are compared to those declared when this shared memory partition was initially managed; if they don't match, psmwatch immediately terminates. If interval is zero, psmwatch merely prints a current usage summary for the indicated shared-memory partition and terminates. psmwatch is helpful for detecting and diagnosing memory leaks. For debugging the ION protocol stack: shared_memory_key Normally "65281", but might be overridden by the value of wmKey in the .ionconfig file used to configure the node under study. memory_size As given by the value of wmKey in the .ionconfig file used to configure the node under study. If this value is not stated in the .ionconfig file, the default value is "5000000". partition_name Always "ionwm".
"0" psmwatch has terminated.
No configuration files are needed.
No environment variables apply.
The following diagnostics may be issued to the ion.log log file: Can't attach to psm. ION system error. One possible cause is that ION has not yet been initialized on the local computer; run ionadmin(1) to correct this. Can't start trace. Insufficient ION working memory to contain trace information. Reinitialize ION with more memory.
Report bugs to <firstname.lastname@example.org>