[OpenAFS] Server upgrade time; which is the right way?

Jeffrey Altman jaltman@secure-endpoints.com
Thu, 25 Oct 2007 18:44:06 -0400

Mitch Collinsworth wrote:
> On Thu, 25 Oct 2007, Jeffrey Altman wrote:
>> File locking is simulated in the client.  The client obtains a full file
>> lock from the file server and then doles out byte range locks locally to
>> the application.
>> The change in the file server from 1.2.13 to 1.4.5 will provide you with
>> large file support and a modification to the locking semantics so that
>> users that have 'w' permission do not need to explicitly have 'k'
>> permission.  Of course, if you have already granted 'k' permission to
>> your users there will be nothing gained.
> No kidding...  I knew about the simulated byte-range locks using full file
> locks bit, but I don't remember knowing that giving users 'k' will
> accomplish the same thing.  Do we really need to be at 1.4.5 to get the
> new locking semantics?  I thought the locking support change happened
> earlier.

The locking semantic change occurred in 1.4.2.   However, you will want
to use 1.4.5 when it is out tomorrow.

Jeffrey Altman