HP3000-L Archives

May 2000, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"VANCE,JEFF (HP-Cupertino,ex1)" <[log in to unmask]>
Reply To:
VANCE,JEFF (HP-Cupertino,ex1)
Date:
Thu, 11 May 2000 12:00:17 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines)
There is a patch coming (don't know its id) that will allow
the AM to abort processes in his/her account via kill. So,
SM can kill any user process, AM can kill all processes in
her account and an ordinary user can kill (via the shell's
kill command) any user processes logged on to the same
user.account (independent of the JOBSECURITY setting).

FWIW,
 Jeff

> I wasn't to happy with inetd logging on as MANAGER.SYS, so
> being a user of
> MPEX/3000 and SECURITY/3000,
> I altered the job to logon as OP.SYS, but allowed OP.SYS to obtain SM
> capability ONLY for the run of the inetd program.
>
> Obviously, with Greg's and Doug's comments on 'the aborting
> user requires SM
> and must be the same as the user the job logs on with', I was
> both trying
> the wrong user but had SM, and the right one without SM.
>
> Dilema time.
>
> Do I change the user back to MANAGER.SYS, or leave as OP.SYS,
> but run GOD everytime I want it dead?

ATOM RSS1 RSS2