Proc::ProcessTable

[Jonathan Lohrmann]

Using module Proc::ProcessTable to manage processes running on HP11.00 produces only processes of UID 0. Same module on HP10.20 seems to work just fine. Any ideas on how to get this module to yield pids for all uids?
Thanks,
Jonathan

use Proc::ProcessTable;

$ref = new Proc::ProcessTable;

foreach $proc (@{$ref->table}) {
print $proc->{pid}, ": ", $proc->{uid}, "\n";
}

[H.Merijn Brand (procura]

You need a small patch. I don't have it handy here, but I'll post it asap with a sample application. 0.35?

[H.Merijn Brand (procura]

Fetched it. Here's the modified package. Use

# bzip2 -d
to unpack. You can get bzip2 from several places, and on my ITRC home https://www.beepz.com/personal/merijn

next mail will have the application posted.

[H.Merijn Brand (procura]

Here's the app. It's called 'px' and I use it as a replacement for 'ps'. Not all options are supported, but filters are builtin

[Jonathan Lohrmann]

There was a java error with the patch. Can you resend the path where I can download the patch? Is this a modified version of the .35 patch or does it go by a different name?

Thanks!!

[Jonathan Lohrmann]

I've loaded the .37 module into perl and I'm still getting only the root pids.

Any other ideas or things I should check?

I noticed the .35 change notes allow the non-root users to list processes for IRIX, but I didn't see any changes like that listed for .37.

Is there a separate patch that needs to be installed?

The module that you included with your reply, is that the px?

[H.Merijn Brand (procura]

> I've loaded the .37 module into perl and I'm still
> getting only the root pids.

> Any other ideas or things I should check?

> I noticed the .35 change notes allow the non-
> root users to list processes for IRIX, but I didn't
> see any changes like that listed for .37.

Changes are all listed as changes to the previous build. Major change from 35 to 37 is the cmd => cmdline name change for hpux

> Is there a separate patch that needs to be
> installed?

No

> The module that you included with your reply, is
> that the px?

Yes, but it is not a module, but a script. Save it to a file (named px), reformat for better readability (unless you can read the attached px from my second post with attachment here) and then

# chmod 755 px
# ./px

and see what happens. Otherwise it's a question of how well you can debug, I guess ...