[Samba] Oplock problem

[Rashkae]

In this case, I would disable oplocks.  My earlier post was only to point
out that with Samba, you can disable oplocks selectively on files that
might cause problems.  Such as database files, or whatever strange
activity you're seeign here.  (Note: Are there multiple computers
accessing the file when you get this 30 second lockup?  If this is a
client locking itself up, there might be a protocol quirk in Samba causing
it.)

On Thu, 8 May 2003, Boogerman wrote:

Yes, you're probably right. Still, we haven't solved that annoying 30 second
lockup problem. This is a very ugly problem. The office network users' keep
yelling at me because of that!

Is there a way to fix this? (I know, I know, it's a client bug, but is there
a server workaround for it?)

Regards,

Gaston Dassieu Blanchet
boogerman at interar.com.ar

----- Original Message -----
From: "Rashkae" <rashkae at tigershaunt.com>
To: "Boogerman" <boogerman at interar.com.ar>
Cc: "John H Terpstra" <jht at samba.org>; <samba at lists.samba.org>
Sent: Wednesday, May 07, 2003 10:21 AM
Subject: Re: [Samba] Oplock problem


> I've never been comfortable with the concept of oplocks myself.  But I
> would like to point out that, unlike Windows, Samba allows fine grained
> control over what shares, dicrectories files or groups of files to allow
> or disallow oplocks on.  If I were to take the time to performance tune a
> Samba server, I would only disable opolocks on those files that are likely
> to be opened read-write by multiple users.  (Database files, as the most
> comon example.)  Performance improvements from oplocks are impressive,
> and the load on the network is greatly reduced.