🚀 go-pugleaf

don@zl2tnm.gen.nz writes:
>
>In article <009631D4.196251A0.31400@WKUVX1.BITNET>, Hunter Goatley
> <goathunter@WKUVX1.BITNET> writes:
>> There is a way to avoid these too.  I had to do this once for software
>> that I didn't want $DELPRCed, $FORCEXed, *or* suspended.  Set the
>> following bits in the PCB:
>>
>>         PCB$V_SUSPEN            !Suspend is pending
>>         PCB$V_DELPEN            !Delete is pending
>>         PCB$V_FORCPEN           !FORCEX is pending
>
>Neat.
>
>        =TOYVAX=> stop "_TWA6:"
>        =TOYVAX=> set proc "_TWA6:"/susp
>        %SET-E-NOTSET, process _TWA6:, PID=00001216, not suspended
>        -SYSTEM-W-NONEXPR, nonexistent process
>        =TOYVAX=> sh proc "_TWA6:"
>        %SYSTEM-F-SUSPENDED, process is suspended
>
>That should confuse 'em.
>
8-)  Yeah, I forgot to mention that $DELPRC will return successfully
when DELPEN is set.  That's what made this fun---with a security
package I once worked on, people would try to STOP/ID the detached
process and would get frustrated wondering why it didn't go away....

Hunter
------
Hunter Goatley, VMS Systems Programmer, Western Kentucky University
goathunter@WKUVX1.BITNET, 502-745-5251