🚀 go-pugleaf

Harry Flowers, FLOWERS@MEMSTVX1.MEMST.EDU, writes:

>In article <8435732@MVB.SAIC.COM>, "CCF::GPE%hermes.mod.uk"@relay.MOD.UK writes
   :
>> Ian Kitching    (systimk@uk.ac.anglia.va) wrote:
>>
>>>However... I know SET WATCH FILE worked under VMS V5.0 but it hasn't worked
>>>for me since V5.2. I've eliminated lack of CMEXEC privilege as the problem.
>>>SDA shows the cell as containing %Xfa00 - an appropriate value for process
>>>default protection. When I use SET WATCH FILE the cell doesn't change.
>>
>> I can confirm that SET WATCH FILE still works under VMS 5.4-3 and A5.5.
> Perhaps
>> they have changed the cell which is used?
>
>One thing I found out when trying to use it is that it requires CMKRNL as an
>AUTHORIZED privilege.  I used Ehud's PRCPRV to give an account CMKRNL to use
>SET WATCH, and it wouldn't work.  So, if you've got CMKRNL as a default priv,
>but not an authorized one, I don't believe that it will work.

I've installed SYS$SYSTEM:SETWATCH.EXE with CMEXEC, to allow non-priv'd users
to trace (vendor-supplied) images.  Haven't had a crash yet, but then again,
it isn't used very often.  I don't know if there are any back-doors to
installing this image with privs, though (like ANALIMDMP's problem).

You could install SETWATCH.EXE with CMEXEC, and put an ACL on the file
preventing non-priv'd users from running it.  Then, if someone needs to trace a
program's file accesses, you can SET RIGHTS/ENABLE/IDENTIFICATION=pid their PID
to grant them the ability to use SET WATCH for this interactive session.

SET WATCH has worked on VMS V5.4-x and V5.5 for me.

-Dan Wing, DWING@UH01.Colorado.EDU or WING_D@UCOLMCC.BITNET (DGW11)
 Systems Programmer, University Hospital, Denver