From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Lee <splee@plexio.com>
Subject: Re: dosemu locking capabilities
Date: 06 Nov 2002 13:13:50 -0800
Sender: linux-msdos-owner@vger.kernel.org
Message-ID: <1036617231.16604.3.camel@ralph.plexio.private>
References: <Pine.SOL.4.31.0211062240170.920-100000@pitsa.pld.ttu.ee>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <linux-msdos-owner@vger.kernel.org>
In-Reply-To: <Pine.SOL.4.31.0211062240170.920-100000@pitsa.pld.ttu.ee>
List-Id: <linux-msdos.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: dosemu <linux-msdos@vger.kernel.org>

On Wed, 2002-11-06 at 12:58, Siim Vahtre wrote:
> 
> How much ways dosemu actually knows to lock one file?
> 
> As I mentioned already, I need quite special way of locking files (paradox
> databases). It must be able to lock one certain record, that is being
> changed, and leave every other record readable/writeable.
> 
> Can dosemu handle it in any way?
> (I'm not sure even if DOS can...)
> 
> Atm, I have tried thousands of different ways to do it (many different
> versions of samba, dosemu, freedos/drdos, etc) but I have not been able
> to (even not for once) get different locking than just this simple
> "OpLocks: none" and "DenyMode: DENY_NONE", which basicly is quite
> 'nothing' for me. (It doesn't forbid anyone to corrupt the data.)
> 
> Am I doing something totally wrong or isn't it really possible to be able
> to lock files in more complex way? (The Windows boxes using the same
> samba fileserver locked correctly, so it must be dosemu's problem, right?)
> 
> I'm really sorry if I'm just wasting your time with stupid questions but
> all those long hours with 'gain: zero' are getting depressing ;-)

Hang in there ;-) I use Foxpro so the locking requirements look to be
different than for Clipper. Hopefully the developers can chime in and
ask for some diagnostic output.

Stephen