Mike Mason <mmlnx@us.ibm.com> writes:
I wrote the attached script [long ago!] in response to a customer
question. They wanted to know if SystemTap could show them which set
of java processes were consuming the most resources, based on the
process arguments. [...]
Reading over this old script again, I'd take away the following
observations:
- process argument fetching routines would be welcome the tapset library
- a syntax to initialize a systemtap array would be useful - both at
compile time ("global array[maxsize] = [idx]=value, [idx2]=value2")
and at run time (module option string "[idx]=value, ...")
- some systemtap policies/libraries have become more favourable to this
kind of script since January.
- a new script that exploits these hypothetical features would be much
more compact and may still make the shell script wrapping unnecessary
- FChE