Re^6: Working With The Process Table (AIX)

[Limbic~Region]

in reply to Re^5: Working With The Process Table (AIX)
in thread Working With The Process Table (AIX)

philipbailey,
We seem to be speaking past one another. At no point have I said the in-house developed script needs to know if itself is running. While the scripts my co-workers may write are in-house scripts, they will be interacting with the process table and any process that may be running there. One (of many) features I would like this library to have is the ability to answer questions like:

• Is /usr/bin/hello running (even if it may look like sh ../hello in the process table)
• Of the bazillion /usr/bin/java processes that are running, are any running with command line arguments that have the max heap space set to above 3GB

I assure you that I read your post carefully and I am sorry if I came across at not being appreciative of your response. Perhaps I am too close to the problem. To try and be clearer - the library is a general purpose way for in-house developed scripts to interact with the process table - even when those processes are not in-house.

[philipbailey]

Limbic~Region, thanks for your more considered reply, and I'm sorry that I partially misunderstood your situation. But I do have some insight into your problem, as we too have a number of other people's Java processes running. In our case, however, we control every aspect of the startup of a customer's code, including the JVM arguments. So we already know what heap size is being used, for example. We are also able to use Unix usernames with enough granularity to identify processes, perhaps in combination with some other piece of data: the PID or part of the command line, with complete certainty. We also always wrap vendor products' code with our own scripts.

Of course, I can't tell whether any of the above can be applied to your situation, but I wish you luck in resolving it.