[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

2398.0. "Accessing shared drawer" by ANGLIN::HARRIS (Let the party begin...) Thu Mar 11 1993 17:18

    ALl-IN-1 3.0, VMS 5.5-2
    
    Customer is creating a shared drawer called BULLETIN BOARD.  she is
    giving *LOCAL read access to the drawer.
    
    the MANAGER can see the drawer, but some non-prived users cannot.  they
    have logged out of the system entirely and still cannot see the drawer.
    The creater of the drawer has also logged out of system and logged back
    in.
    
    the non-prived users are logged into the same node where the drawer was
    created.  the ACL shows w:E access. 
    
    to find the drawer, the non-prived user enters FC SDR
    for the name of the drawer, they enter  [ALL-IN-1 username]drawer name{FIND}
    
    any ideas?
    
    	ann
T.RTitleUserPersonal
Name
DateLines
2398.1Known bug -- thr-16453CHRLIE::HUSTONThu Mar 11 1993 18:238
    
    There is a known bug in the FCS that it does not respect the
    *LOCAL rights. THe FCS basically does not respect any rights
    id's except those that are explicitly granted to a user and 
    stored in the rightslist.dat entry for that user.
    
    --Bob
    
2398.2ANGLIN::HARRISLet the party begin...Thu Mar 11 1993 18:474
    so, are you saying that NO groups can be used to assign access to
    regular shared drawers?  will this be "fixed" later?
    
    ann
2398.3Groups work fineCHRLIE::HUSTONThu Mar 11 1993 19:1311
    
    *LOCAL is not a group. It is a VMS rights ID that is assigned by 
    VMS to processes that are truely local (not set host in). The FCS
    simply overlooked assigning it.
    
    Will it be fixed? Wrong conference to ask in. All I can say is that it
    is in the official bug list, so we know about it. If lots of people 
    complain about it, then it will get moved up the fix list.
    
    --Bob