| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2476.1 | I can wait 1 minute | AIMTEC::WICKS_A | Oscar the Grouch is an Optimist! | Fri Mar 26 1993 00:58 | 16 |
| Normand,
Almost a whole minute! was this on a VAX9000?
Flogging would be too good for the developer responsible (:==:)
If you put trace on you'll see lots of calls to the DCL functions
SET FILE/PROT, CREATE/FDl and calls to the ALL-IN-1 ACL function on
numerous files - take a look at the script FC_DRAWER_SHARE in OA$DO.
It really has an awful lot to do and I personally don't mind waiting.
Regards,
Andrew.D.Wicks
|
| 2476.2 | Clarifying and guessing wildly! | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Fri Mar 26 1993 08:49 | 14 |
| Whilst Andy's description of the process is accurate, I'm not if that's
what .0 was complaining about.
Are you (.0) saying that after the person who grants the access has got
command back (i.e. after the "Working . ." message has gone away, and
the cursor has returned), the person granted the access can't get in
for a minute after that?
Was a group being used?
Perhaps the file cab server had cached the person's SYSUAF info. and it
needed to be updated?
Graham
|
| 2476.3 | FCS caches drawer security info | CHRLIE::HUSTON | | Fri Mar 26 1993 13:59 | 28 |
|
If .1 is correct and you are saying it takes up to a minute for control
to be given back to you, then see what .1 says, changing the protection
on a drawer and its documents does ALOT of work.
If .2 is right and you are saying that after you get control, there
is a delay in when you can use the new access stuff, then .2 is right
IF you are doing something that uses the FCS, like non-MAIN drawer
operations. The FCS maintains a cache of open drawers, one of the
items it caches is the security information of that drawer, like the
ACL on ACCESS.DAT, drawer owner, protection mask etc. This information
times out by default every 10 minutes and the next access to the
drawer requires it to be re-read and you will pick up the new access
information. The timeout length can be set by the Set/Show server
calls to the FCS and passing OafcT_SysManAuthTimeout, it is in
seconds and comes with a default of 600 (10 minutes).
If the FCS is used to set the access on the drawer then the cached
security information is automatically flushed and re-read so there
should be no delay. I don't believe that IOS uses the FCS to set the
security information and there is no communication between the FCS
and IOS to tell each other when one of them has changed the security
information.
Make sense?
--Bob
|
| 2476.4 | not during... after | MQOSWS::N_CARDELLA | Father of Tiger | Fri Mar 26 1993 16:18 | 14 |
| uh... .2
After the "grantor" gave access to a person (as part of a group), and
his terminal was cleared for more work, the second person couldn't
access the file for about 1 minute.
Personally, I have no problems with the wait... like what difference
does it make (?), but I have a customer who is quite inflexible. He is a
PROFS user (and loves it), and his boss sent him to us to check out
ALL-IN-1 because their IBM mainframe is costing them a mint in
maintenance charges... what else is new. I am just trying to answer
all his questions so that he can finish his report.
Normand
|