Craig:

Yeah, I know about the possibility of a username/rights_id conflict. 
The problem is in my installation, we make _major_ use of rights ID's,
and very often a

  write sys$output f$getjpi (blah, "rightslist")

will overflow and error.  So I kind of have to do a show process ...

I also looked at Dan's vms::process missing the RIGHTSLIST item.  It
appears that it may be because of:

a) the rights list size is unknown going into the (single) $getjpi call
he does, and he static allocates everything
    (okay, so just preallocate a "big honk'n buffer" (tm))

b) After retrieval, they have to be converted from int id's into strings
ot be useful back in perl.  Straightforward, but "yet more code" (tm)

This is actually where my recent question came up about upgrading perl. 
I was going to patch this, but I discovered that somewhere along the
line I must have accidentally nuked critical parts of my perl
installation, like "perl.h".  

So, if I have to reinstall perl anyway, why not just upgrade ...

-- Pat

p.s.  My VMS::Process and VMS::Device wet dream, otoh, is to be able to
get process and device information from other nodes in the cluster ...

"Craig A. Berry" wrote:
> 
> At 12:56 PM 11/22/2000 -0600, Patrick Spinler wrote:
> 
> >Here's a recent example which I have just finished.
> 
> Very cool, Patrick.  There is a remote possibility that a user name or node
> name in the output of SHOW PROC/RIGHTS could match a rights identifier, so
> you'd probably be a bit safer replacing the line:
> 
>         $origprocrights = `show proc /rights /id=$hexpid`;
> 
> with something like
> 
>         $origprocrights = `write sys\$output f\$getjpi("$hexpid","rightslist")`;
> 
> The backquote and the spawn this involves shouldn't be necessary except that
> VMS::Process for some reason doesn't implement JPI$_RIGHTSLIST; I'm going to
> look into putting it in, though if Dan skipped it there may be a good reason.

-- 
      This message does not represent the policies or positions
             of the Mayo Foundation or its subsidiaries.
  Patrick Spinler                       email:  [EMAIL PROTECTED]
  Mayo Foundation                       phone:  507/284-9485

Reply via email to