Subject: | |
From: | |
Reply To: | |
Date: | Tue, 11 Sep 2001 07:05:48 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
At 07:45 AM 9/11/01 -0400, Paveza, Gary wrote:
>How about a lockword on the command?
The method of managing access to higher-level CI commands in MPE is
by capabilities. I'm not keen on changing it, but would rather
remain consistent.
>Also, any user with OP or SM capabilities should be tightly controlled.
As should always be the case as today.
For those that do remote management of a system, the ability to shutdown
and restart the box using this method offers advantages over trying
to locate an individual and walk them through the process.
I do think that having a confirmation step associated with the CI-based
shutdown prompt would be helpful in preventing possibly mistakes. The same
isn't really needed when doing this via a CNTL-A on the console as this
method is a little more obvious (with the location restruction and use of
the cntrl-A key sequence) and less prone to the same type of mistake.
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|