Hi Jeff, On Mon, 23 Apr 2007, Jeffrey Altman wrote:
> Thomas Mueller wrote: > > we used to have a directory with this ACL entry > > > > system:authuser li > > > > so that users with a valid token may drop their files here, but no-one > > will be able to read, modify, delete or overwrite existing files. > > With the 1.4 clients this works fine. > > > > Now I found that the 1.5.18 client (on Windows - no other versions > > checked) requires that the "w" permission must also be set to insert new > > files - but this allows the modification of existing files too. > > > > Are my observations correct? > > If so, was it intended and why? > > > > 1.5.x obtains locks from the file servers whereas 1.4.x did not. > > The 'l' permission controls read locks not write locks. Write locks > are controlled by the 'w' permission or the 'i' permission of the client > owns the file. > I see, thank you for explaining. > The behavior is not intended. If it is the case, please file a bug > report to [EMAIL PROTECTED] no, I would prefer the behavior of the 1.4.x client ( 'i' permission should be sufficient to create a file within a directory) - so I rather would consider the current behavior of the 1.5.x client as a bug. Would you like to see this as a bug report in [EMAIL PROTECTED] Thomas. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
