| Raimund,
I have reproduced the ABS SET ENVIRONMENT problems that you are seeing
with the current version.
I have entered a qar for this (#1902).
If you have multiple entries for a specific node::user, it will
pick the first one that matches. So, in your case, it would have
used the one with no access listed.
Thank you for reporting the problem.
I will have the GUI maintainer reply with an answer to the GUI
problems.
Chris
|
| Hi Raimund,
I'll be answering question number 3:
>>3. Knowing that under some circumstances the GUI gives better results
>> I tried to use it to get rid of the additional ACCES_RIGHTS
>> entries. I tried to use it to get rid of the additional ACCES_RIGHTS
>> entries.
>>
>> So I started the GUI
>> selected the ENVIRONMENT to modify
>> choosed ACCESS CONTROL
>>
>> and because I tried several strings with the same Node::Account Pair
>> all of them where listed in the appropriate Window.
>> Needing just one of them I selected one ,pressed the DELETE Button->
>> it dissapeared.Next one select Entry,DELETE -> the GUI dissapeared with
>> Starting the GUI again ->the Acces Control List remained unchanged.
>> Further investigations brought to daylight that it's enough to select
>> one of the equal pairs and delete it. Although just one entry
>> dissapears from the Window the hole List is deleted of confirm the
>> deletion for the one by finishing the Object modification.
Yes, the GUI as MANY problems and we are currently in the process of
replacing the current GUI and are focusing our efforts in that
direction at this very moment. Therefore, little to no resources are
allocated to the "old" GUI. With problems that come up, my attempts
are to find workarounds.
I attempted to reproduce the crash you experienced but was unable to do
so. However, this is nothing uncommon. The GUI will work sometimes
for me and then other times it will crash doing an identical task.
It also depends on the machine.
I'm not sure if I completely understand your last statements, are you
saying you attempted to delete just one at a time and still ran into
the same problem.
If you need a workaround, my first suggestion would be to try deleting
one at a time. Otherwise, use DCL.
Does this help you?
Thanks, Mickey
|
|
Hello,
and thanks to both of you for your immediate response.
Anyway,I didn't expect a solution to that, I just wanted to
make you aware of it.
Regarding to .2:
Sorry for the description (which does not clearly bring out what the
problem is).
Hope the 2'nd one is better...
After using the following commands to modify the EE
ABS> SET ENV DISASTER_RECOVERY_ENV/ACCESS_RIGHTS=-
(USER_ID=*::RTSSOPS,ACCESS="READ,WRITE,SET,SHOW,DELETE,CONTROL,EXECUTE")
ABS> SET ENV DISASTER_RECOVERY_ENV/ACCESS_RIGHTS=-
(USER_ID=*::RTSSOPS,ACCESS="READ,WRITE,SET,SHOW")
ABS> SET ENV DISASTER_RECOVERY_ENV/ACCESS_RIGHTS=-
(USER_ID=*::RTSSOPS,ACCESS="DELETE,CONTROL,EXECUTE")
ABS> SET ENV DISASTER_RECOVERY_ENV/ACCESS_RIGHTS=-
(USER_ID=*::RTSSOPS,ACCESS="DELETE,CONTROL")
ABS> SET ENV DISASTER_RECOVERY_ENV/ACCESS_RIGHTS=-
(USER_ID=*::RTSSOPS,ACCESS="EXECUTE")
there is a list of "*::RTSSOPS" Entrys like
Execution Environment
Name - DISASTER_RECOVERY_ENV
Version - 3
UID - C95C5EB8-D1A6-11D0-8007-AA0004001CFC
Data Safety Options - FULL_DATA_VERIFICATION,
XOR_REDUNDANCY_GROUPS,CRC_VER
IFICATION
Listing Option - NO_LISTING
Span Filesystem Options - SPAN FILESYSTEMS
Symbolic Links Option - LINKS_ONLY
Compression Options - None
User Profile
Node - ALPH1
Cluster - *
User - ABS
Privs -
Platform ID - 0
Access Right - None
Owner - ALPH1::ABS
Access Right - ALPH1::ABS
Access Granted - READ, WRITE, SET, SHOW, DELETE, CONTROL,
EXECUTE
-> Access Right - *::RTSSOPS
-> Access Granted -
-> Access Right - *::RTSSOPS
-> Access Granted - READ, WRITE, SET, SHOW
-> Access Right - *::RTSSOPS
-> Access Granted -
-> Access Right - *::RTSSOPS
-> Access Granted - DELETE, CONTROL
-> Access Right - *::RTSSOPS
-> Access Granted -
Notification Method - NOTIFY_OPERATOR
Notification List - TAPES
Notification Reason - ON_FATAL_ERROR_CONDITION
Notification Method - NOTIFY_BY_MAIL
Notification List - <REQUESTER>
Notification Reason - ON_FATAL_ERROR_CONDITION
|
v
Now the GUI is used to get rid of the additional entries.
First the EE is selected (as an object which has to be modified)
then the ACCESS CONTROL... Button is pressed
and in that window -> one of the "*::RTSSOPS" entries is selected
the DELETE Button is pressed
-> the entry on the displayed list disappears.
If I select another of those "*::RTSSOPS" entries from the List and
press the DELETE Button again -> the GUI crashes.
As a workarround the SET Operation is finished after the first entry
has been removed(as you already described).
After that -> the whole list of "*::RTSSOPS" entries for this EE
disapeared.
raimund
Ps: how to remove those entries one by one using DCL ?
Hope that this describes the
|