I've got a client using a Samba server to hosts DBFs used in a
multi-user order entry and accounting application. Sometimes things
don't work right. The operators insist "I didn't do anything" but we
know they reboot once in a while and also there seems to be a point in
their application (20-year-old FoxBase code) where the system crashes,
although we are remote and haven't yet got sufficient instrumentation
to figure out all of the details.
I wanted to make sure I've got the Samba configuration correct for
multi-user locking; there's usually only one developer here in the
office using an app, and we usually all just develop on our own
machines, so the infrequent testing on our in-house Samba shares is
certainly not conclusive. Has anyone found an authoritative reference
that recommends the use of the 'oplock' or 'spinlock' directives in
smb.conf for successful VFP operations? Or know conclusively they are
not needed? It would be good to eliminate this as a possible cause of
their data problems.
tia.
A typical programmer likes to blame it on the network, but in this
case I'm the network sysadmin too.
--
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
©2008 Ted Roche |
