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

[Barry Smoke]

We use an educational software package called Accelerated Reader, and it
uses a foxpro database.  Our administration uses a second foxpro program
for accounting, but there is only one user for that one....
But Accelerated Reader can have 30-60-100 users at a time, and after
months of research, we figured out how to tweak our server's smb.conf
file to work the best with the program.

We used a veto oplock files =
/arcerttb.*/arclass.*/arenroll.*/argoaltb.*/arhtsqiz.*/arriquiz.*/arrpqu
iz.*/arstu.*/repsttng.*/ripubsi.*/sndmatch.*/student.*/cfg.*/arqbrtb.*/a
rptstb.*/alsbigc.*/

Config line on the share we are using....that is not all the files in
the program, and we found that it was only necessary to veto oplocks on
these files.....because the rest benefited from the oplocks....

When we did this....poof no more AR problems....it has been stable for
months now.

It would have been nice if samba handled these files correctly, and I
sure am going to test 2.2.4 when it comes out, without these lines.....

Great to hear our problems have been duplicated with foxpro files....




-----Original Message-----
From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]
On Behalf Of Jeremy Allison
Sent: Tuesday, March 26, 2002 12:14 PM
To: Jason Barker
Cc: Pablo Alcaraz; samba at lists.samba.org
Subject: Re: [Samba] FoxPro/lock troubles with samba 2.2.2/.3a

On Tue, Mar 26, 2002 at 09:31:02AM -0700, Jason Barker wrote:
> 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.

That's probably the best idea. I was given a program the stressed
the Foxpro locking code over a network severely and it was
failing on Samba, the change I made fixed it and will be in
the next release (2.2.4). If you're not experiencing problems
currently then no need to upgrade to (still changing) CVS
code.

Jeremy.

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba