I will look at reworking the PROCS data to match 'ps -ef'. The
user/procs count used to be obtained by bigbrother from the messages in
the CPU test.
CMD is irrelevant for most of the PROCS (service virtual machines) on
z/VM, but for a real user, we could get the last command buffer.
TTY could be filled in with the LUNAME, terminal device number or 'DISC'
to be meaningful.
/Thomas Kern
/XXX-XXX-XXXX
-----Original Message-----
From: Rich Smrcina [mailto:user-cf452ff334e0@xymon.invalid] Sent: Thursday, October 19, 2006 11:56 AM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] format for CPU data?
Then for procs you may need to present that data is 'ps -ef' format:
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Oct18 ? 00:00:01 init [5]
root 2 1 0 Oct18 ? 00:00:00 [ksoftirqd/0]
root 3 1 0 Oct18 ? 00:00:00 [events/0]
root 4 1 0 Oct18 ? 00:00:00 [khelper]
root 9 1 0 Oct18 ? 00:00:00 [kthread]
root 19 9 0 Oct18 ? 00:00:08 [kacpid]
root 116 9 0 Oct18 ? 00:00:00 [kblockd/0]
root 156 9 0 Oct18 ? 00:00:00 [pdflush]
Some of the data here doesn't really apply to z/VM, but it should be possible to come up with some sort of value for each column. UID and CMD would probably be the same thing, PID can be a counter, PPID would be 1, STIME would be the logon date or time, TTY is not relevant and TIME would be the CPUTime.