[Samba] FoxPro/lock troubles with samba 2.2.2/.3a

[Jason Barker]

You are certainly right about "if you do not have problems...", that's why
we ran some checks, and the database checks out fine.
This database is 20MB in size and it accessed by a FoxPro5 front-end that
someone in-house wrote. During the day there is anywhere between 5 to 15
users accessing it. We've been running the database off of the samba server
since the first half of February, with no problems. Reading about these fox
pro corruption problems still concerned me though, but everything is looking
OK. Since it is all working fine, and has for almost 2 months now, I am just
going to keep an eye on it, and upgrade at the next release rather than grab
the CVS.

Thanks for everyone's help.


-----Original Message-----
From: Pablo Alcaraz [mailto:pabloa at laotraesquina.com.ar]
Sent: Monday, March 25, 2002 9:27 PM
To: Jason Barker
Cc: samba at lists.samba.org; jra at samba.org; pabloa at mbasystems.com.ar
Subject: Re: [Samba] FoxPro/lock troubles with samba 2.2.2/.3a


You know, if you do not have problems, do not repair it ;-)

We have *huge* foxpro databases. They are accessed with 16bits, 32bits 
and dos applications and they are accessed for 10-15 users in the same 
time. The users do a lot of modifications in the data. I think is not a 
common escenario.

The speed problem is happen with 2.2.2 and 2.2.3a versions.


Jason Barker wrote:

>Ouch, I haven't heard anything about these FoxPro corruption problems, been
>away from the mailing list for 3-4 weeks.
>
>I am very interested in the outcome of this, I am managing a Samba 2.2.3a
>server for the company I work for, and so far we have had no problems. I
set
>the server up back in January with 2.2.2 and upgraded to 2.2.3a, and once I
>had everything setup how we wanted it, a lot of stuff was moved on to it,
>including the company's bugs database which uses FoxPro. So far, there have
>been no problems, and no one has noticed any corruption, but after hearing
>about these problems, I am going to see about doing a more thourough check.
>
>It sounds like Jeremy is pretty sure he has fixed the problem, and I
>certainly hope so. I took a quick look around the CVS through CVSweb and
>noticed that you made changes to locking.c to fix this problem. I am
>thinking about upgrading Samba 2.2.3a on the server to a version that has
>this fix, and was wondering, would you recommend I download the latest
>SAMBA_2_2 from CVS. Or can you tell me what files for this fix to grab (if
>there are more than just locking.c) and then recompile 2.2.3a with them. I
>only ask because I want to keep any new problems that could be created by
>the latest CVS code to a minimum, since 2.2.3a seems to be working fine for
>us. But at the same time would like to kill this problem before it has a
>chance to bite us.
>
>Also, is there some place to get Gerald's test program?
>
>Oh, and Pablo, did you encounter the speed problems AFTER upgrading to the
>Samba CVS version?
>
>Thanks.
>
>
>-Jason B.
>