3.2.7 vs 3.5 locking logic/mechanism - locking denied to non-owners

[lejeczek]

I've done some tests one SL6.1 with:

3.3.8 (originally el5.1) - problem exists

3.2.11-0.31.el6 (originally fedora9) - free from this problem

so it seems like something definitely changed between, 
possible from 3.3 up

how one not being a programmer troubleshoots/debugs such a 
problem?
also
security-wise, would it be safe to stay with 3.2.11 these 
days? even if feature and performance-wise this older 
version may lag behind latests ones?

thanks


On 27/04/12 10:21, Volker Lendecke wrote:
> On Fri, Apr 27, 2012 at 10:01:34AM +0100, lejeczek wrote:
>> what I'd like to have working OK is that client accessing a 3.5
>> read-only share like 3.2.7 does, regardless of permissions, meaning
>> not needing to be the owner (which sort of makes no sense since it's
>> read only, right?)
> If it's guaranteed to be a read only share, you might want
> to try "share modes = no". Be aware that this severely
> breaks SMB semantics, but at least with a read only share
> you won't corrupt your data.
>
> Volker
>