RE: CLIPPER LOCKS

["Matthew Nuzum" <cobalt@bearfruit.org>]

I had a similar problem with 0.98.  I was using MS Dos 6.2.  I fixed it
by going to the newest version of Samba.  This may or may not be your
solution, here are my details:

DOS program was hosted on Linux Server.  People accessing the
application through a Windows computer (via a Samba share) had serious
locking/not locking issues.

I think my problem was due to Samba 2.0 and going to the (then) new 2.2
fixed it.

Matthew Nuzum
newz@cyberdude.com
www.bearfruit.org

> -----Original Message-----
> From: linux-msdos-owner@vger.kernel.org [mailto:linux-msdos-
> owner@vger.kernel.org] On Behalf Of Anderson Pereira Ataides
> Sent: Friday, June 14, 2002 11:21 AM
> To: linux-msdos@vger.kernel.org
> Subject: CLIPPER LOCKS
> 
> Hi,
> 
> I've got an application develop using Clipper 5.01 and I'm having
trouble
> with locks.
> 
> When I lock a file (or record) in one workstation using Windows
another
> workstation can not open the same file, that's ok. But when I lock a
file
> in
> the same workstation, my Linux + Dosemu does not see that file is
locked
> and
> open it anyway. The same problem occurs between two Linux+Dosemu
> Workstations.
> 
> This problem does not happen when two dosemu sessions are opened in
the
> same
> workstation. In this case, file locked in first session can not be
read by
> the second session.
> 
> Because of this problem, my application is loosing data, because of
> concurrent updates to a locked file.
> 
> How can I solve this problem? Is it a dosemu bug?
> 
> I'm using dosemu 1.1.2.
> 
> Anderson Pereira Ataides
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos"
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html