[Samba] How important are oplocks?

Marian Mlcoch, Ing mm at tsmp.sk
Fri Dec 20 06:34:58 GMT 2002

Yes yuo have right with idea that if hardware is bad then oplocks is bad but
my idea is that dbase aplications and engines must known about quality of
network hardware, client and status and must have system to repair or
disable oplocks if is bad ! Nothing another only dbase engine must realise
this operation. If not then this engine is bad and not for network use.

Then must exist list of this engines with realy dangerous level...

Secondary is that yuo write as more aplication open only one user ??? This
is .... then why i need file server?
File servers is created primary for use with database aplications!
Yes sql is best but how many users of samba or NT uses realy network sql

Thats all folks.

----- Original Message -----
From: "Jim Morris" <jim at morris-world.com>
To: "Marian Mlcoch, Ing" <mm at tsmp.sk>
Cc: "Bob Puff at NLE" <bob at nleaudio.com>; "Jean-Paul ARGUDO"
<jean.paul.argudo at pack-solutions.com>; "Joel Hammer" <Joel at HammersHome.com>;
<samba at lists.samba.org>
Sent: Thursday, December 19, 2002 3:22 PM
Subject: Re: [Samba] How important are oplocks?

> On Thu, 2002-12-19 at 03:56, Marian Mlcoch, Ing wrote:
> > Thanks Jim for best report of oplock as i read.
> > Super can be if you can add info or link about list of dangerous
> > engines for oplocks...
> > Btw.  Foxpro 2.6 = is ok.
> >           Foxpro 7.. = bad.
> >           Clipper    =  dangerous...
> > exist this list for off oplocks?
> Thanks. But unfortunately, its not that simple.I doubt for example that
> one version of FoxPro will be good with oplocks, while another is bad.
> The entire problem with oplocks and shared-file databases such as dBASE,
> FoxPro, Paradox, Access, etc, is with file caching on the client side
> (the OPLCOCK), and that client system not breaking the oplock when
> requested.  Even when the breaks do happen properly, the time to write
> the file back out to the server may be significant, causing a LOOOOONG
> delay on the 2nd client to open the file.
> When you see oplock problems, I guess you could say it is more client-OS
> and hardware dependant than it is on the software involve. It just so
> happens that the type of software that runs into oplock related issues
> most often is shared-file database software. Most other applications do
> not have 2 or more users opening the same file at the same time on a
> routine basis.
> --
> /-----------------------------------------------
> | Jim Morris  |  Email: Jim at Morris-World.com
> |             |    AIM: JFM2001
> \-----------------------------------------------
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

More information about the samba mailing list