Henrik,
I'm not sure what you mean by the header. I assume you mean the column headings on normal ps output: $ ps aux |head -1 USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
It appears that the command line ps options that I want to use, drastically change the column header: $ ps -welfm |head -1 F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD
Will hobbit handle this? If not, can I hack it to make it do so? If I have to I suppose I could use a shell script wrapper for ps that wiill spoof a header that the client is expecting.
-Charles
From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Fri 7/28/2006 11:59 PM To: hobbit at hswn.dk Subject: Re: [hobbit] RE: [Hobbit] Using variables in clientlaunch.cfg?
On Fri, Jul 28, 2006 at 11:12:21PM -0700, Charles Jones wrote:
I just thought of another way to do this. I could modify the ps arguments that hobbit uses, and then just use hobbit-client.cfg with the PROC and TRACK options, and then I won't have to deal with using an ext script at all.
$ ps -welfm |egrep '(java.+tc_1_1)'|grep -v grep |wc -l 66
The "m" flag shows all sub processes/threads. Without it, it would only show a single java process.
So this would work, but the question is, would hobbit still correctly parse the ps output with those flags?
As long as it has a header with the same identifier for where the commandline is, then it should work.