WG: oplock problem
andreas.moroder at sb-brixen.it
Tue Nov 13 06:36:04 GMT 2001
you are faster solving the problems then I am to tell you what the problem
Today I made the test first with the 2.2.2 and got the problem as explained
after less than a minute.
I took the latest cvs and tested again. The test di run two hours WITHOUT a
What about to warn the users about this problems an make a interim version
Thank you very much
I have the problem that users in our hospital log in at 7:00 am. Is there a
way to upgrade to a new version of samba without have to make log out all
users ? The last times I was in the office at 6:50.
Von: "Jeremy Allison" <jra at samba.org>
An: "Claudia Moroder" <claudiamoroder at st-ulrich.suedtirol.net>
Cc: <samba-technical at lists.samba.org>
Gesendet: Freitag, 9. November 2001 18:54
Betreff: Re: oplock problem
> On Fri, Nov 09, 2001 at 06:24:02PM +0100, Claudia Moroder wrote:
> > I tested this program too and got the same strange problems. Our Samba
> > server is 2.2.2.
> > Remember, that clipper uses a strange locking trick. It does not lock
> > area it want to lock but 1 byte at a offset of 1GB ( im am not shure
> > the right value ).
> > We have other clipper and paradox apps that worked well with 2.0.7, but
> > index problems today.
> > I have the source of a small testing program Daniel wrote, but at the
> > not the binary ( I have at the office ), if necessary to make tests.
> That shouldn't cause a problem (lock at 1gb). Can you post a binary
> so I can test it here ?
More information about the samba-technical