Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ucbvax!ESOC.BITNET!ESC1318
From: ESC1318@ESOC.BITNET
Newsgroups: mod.computers.vax
Subject: NOTE from ESC1318
Message-ID: <8610150916.AA02784@ucbvax.Berkeley.EDU>
Date: Wed, 15-Oct-86 05:17:03 EDT
Article-I.D.: ucbvax.8610150916.AA02784
Posted: Wed Oct 15 05:17:03 1986
Date-Received: Thu, 16-Oct-86 07:54:19 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 27
Approved: info-vax@sri-kl.arpa

Date: 15 October 1986, 09:02:59 SET
From: ESC1318  (Mike Brett at ESOC)
To:   INFO-VAX at SRI-KL

Many thanks to all those who replied to my question on
mailboxes/acls...but the problem still remains unsolved.
I was asked for more detail , so...

1) use $CREMBX to create a mailbox with W:RWLP "protection"
   anyone can read or write to it.

2) put an ACL on the device :
        (id=mbx_holder,access=read+write)
        (id=*, access=none)

3) get a mbx_holder to read/write to the mailbox --> protection error

4) if I give CONTROL access as well the id holder can change the ACL
   as expected but still can't read or write to the device.


I'm puzzling over whether using the ACL is preventing the holder
logical IO access to the device ??

Thanks for your time.