HP3000-L Archives

May 1999, Week 3

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:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Sat, 15 May 1999 13:12:58 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
Lars Appel wrote:
>
> One of the major obstacles of the Posix KILL command seems to be
> that the killer process needs to run under the same user ID as the
> victim in spe -ahem- target.
>
> I wonder if it would be helpful if someone took some time to create
> a little MYKILL program that essentially uses setuid() before kill()
> to release that restriction...

Or better still, port 'su' to MPE (but that would likely be a biggie
due to the differences in UID resolution between MPE/unix).  But since
you have to essentially 'su' before the 'kill', just stop at the 'su'
and leave it at that, and you have 'su'.

(for the posix-challenged, 'su' is 'set userid'.  In MPE-terms, the
closest equivalent is doing a :remote:localhost hello user.acct to
obtain another user's login which persists until you exit/bye, then
you are back to your original self.  'su' is standard unix, more or
less; and 'sudo' - "set userid and do" does the same thing but does
not require a password for specific commands you may be allowed to
invoke on behalf of another userid.  'sudo' is freeware)

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2