Lars Schimmer wrote: > Hi! > > Just studied the release notes to the 1.4 release. > There is written: > Byte-range locking as described in cm_vnodeops.c has been implemented. > > Does that mean, we can now safely edit MS Office Files IN AFS Space > while all servers/clients are 1.4 versions? > *hoooray* > > Cya > Lars
The Byte Range Locking support has been pulled up to the 1_4_x branch as part of the 1.4.1 development effort. Installers containing this support are now available at http://web.mit.edu/jaltman/Public/OpenAFS/ByteRangeLocking/ /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/ByteRangeLocking/ \\afs\athena.mit.edu\user\j\a\jaltman\Public\OpenAFS\ByteRangeLocking\ As mentioned in the README file stored with the installers, it is crucial the the 'k' privilege be provided to users if you want them to be able to make use of AFS with this release. Almost all Windows applications obtain a shared read lock on files being accessed. Without the 'k' privilege, the application of this lock will fail and files with AFS will not be able to be accessed. This functionality is going to require a serious amount of testing. In particular, testing the execution of complex applications out of AFS is required. I have successfully tested executing Microsoft Office 2003 out of AFS. However, I suspect that other applications may not behave as well as Microsoft's. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
