On 3/18/2011 12:20 PM, Thomas Smith wrote:
> On Fri, Mar 18, 2011 at 7:55 AM, Jeffrey Altman
> wrote:
>> We are all looking forward to the day that the byte-range lock
>> implementation you have been working on can be merged into the tree.
>
> Is there an estimate as to when this may occur?
I am
On Fri, Mar 18, 2011 at 7:55 AM, Jeffrey Altman
wrote:
> We are all looking forward to the day that the byte-range lock
> implementation you have been working on can be merged into the tree.
Is there an estimate as to when this may occur?
___
OpenAFS-in
On 3/18/2011 9:48 AM, Matt W. Benjamin wrote:
> Hi Thomas,
>
> Mandatory enforcement is the defined behavior for byte-range locks on
> Windows. Since you are testing on Windows, you are seeing the Windows
> behavior. The same lock would be interpreted as advisory on a Unix client.
>
> Matt
W
On 3/18/2011 9:29 AM, Thomas Smith wrote:
> Hi,
>
> Is it possible to open files read-only when another process has a
> write-lock? I found the following information regarding 1.5.20.
>
> http://dl.openafs.org/dl/openafs/1.5.20/winxp/relnotes.htm
The release notes for the version of the Open
Hi Thomas,
Mandatory enforcement is the defined behavior for byte-range locks on Windows.
Since you are testing on Windows, you are seeing the Windows behavior. The
same lock would be interpreted as advisory on a Unix client.
Matt
- "Thomas Smith" wrote:
> Hi,
>
> Is it possible to op
Hi,
Is it possible to open files read-only when another process has a
write-lock? I found the following information regarding 1.5.20.
http://dl.openafs.org/dl/openafs/1.5.20/winxp/relnotes.htm
Many applications on Windows (e.g. Microsoft Office) require
the use of byte range locks
