HP3000-L Archives

July 2001, Week 1

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:
Re: inetd and operator.sys, part 2
From:
Michael L Gueterman <[log in to unmask]>
Reply To:
Michael L Gueterman <[log in to unmask]>
Date:
Tue, 3 Jul 2001 13:59:09 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines) 
Donna wrote:

<snip>
>> Maybe an SIB item?
>
>this is an intriguing thought?  should inetd be modified to allow someone
>other than (literally) manager.sys to 'use' it.  given doug werth's
>comments (With inetd, even a user with SM capability cannot kill inetd.
>It appears to be hardcoded for MANAGER.SYS.  My guess would be that it
>started as source from UNIX that was programmed to look for root user (or
>UID 0) and chose to replace it with the closest MPE equivalent of
>MANAGER.SYS or UID 1.), it makes me wonder if it's possible.  i believe
>there is some argument for enabling operator.sys access to inetd though.
>what do 'we' think?         - d
<snip>

I think that either an OP or NM capability user would legitimately
have the right to kill (or reload) inetd.  Especially when your writing
automated shutdown scripts (for a future SHUTDOWN command :), this
would be a reasonable thing to do.

Regards,
Michael L Gueterman
Easy Does It Technologies LLC
http://www.editcorp.com
voice: 888.858.EDIT or 573.368.5478
fax:   573.368.5479
--

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2