[OpenAFS] Making read locks mutually exclusive

Neulinger, Nathan nneul@umr.edu
Wed, 22 Jan 2003 12:18:54 -0600

Yuck. Read locks are not exclusive, by definition. You'll probably cause
lots more problems by making read locks exclusive then you'll solve.=20

Word is probably doing a byte-range lock on the file, which is not
supported by the afs servers. Support could be added to the clients for
byte range locks, but has not yet been developed.=20

-- Nathan

Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-4841
Computing Services                       Fax: (573) 341-4216

> -----Original Message-----
> From: Peter Schuller [mailto:peter.schuller@infidyne.com]=20
> Sent: Wednesday, January 22, 2003 11:58 AM
> To: openafs-info@openafs.org
> Subject: [OpenAFS] Making read locks mutually exclusive
> Hello,
> is there a way to make OpenAFS treat read locks as mutually exclusive,
> other than modifying the source? If no, could someone point me in the
> general directon as to where this stuff is handled on the server side
> (in terms of which part(s) of the source)?
> I'm trying to prevent users of Office and similar Windows=20
> apps to overwrite
> each other's changes. During testing I experienced some unexpected
> behavior.
> If I open a Word document and save it (or create a new one)=20
> one machine
> A, and open it on machine B, Word on machine B will say it's write
> protected [this is the desired, but unexpected, result]. Yet, I
> assume machine A isn't keeping the write lock around after the file
> is written, so why does machine B react like it does?
> If I just open the file on machine A, and then on B, both=20
> will be opened
> in read/write mode (in Word land, not in filesystem land)=20
> [expected but undesirable behavior].
> Thanks,
> --=20
> / Peter Schuller, InfiDyne Technologies HB
> PGP userID: 0xE9758B7D or 'Peter Schuller=20
> <peter.schuller@infidyne.com>'
> Key retrival: Send an E-Mail to getpgpkey@scode.org
> E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org
> _______________________________________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-info