Re: Samba and kernel oplocks

Anderson Pereira Ataides
2002-08-28T13:14:16Z

I have a similar problem here but using CLIPPER not FoxPro. I received some
messages to upgrade kernel and Samba. I made it and I've just tested
(yesterday), but did not solve my problem. Windows workstations still can't
see locks made by dosemu. And dosemu also can't see windows locks.

Just to confirm, I am using:
kernel 2.4.19
samba 2.2.5
dosemu 1.1.3

I thing problem is not only samba because nfs also have problem. I have two
Linux workstations and when I lock record in one of them, the other one can't
see this lock.

Like you I'm waiting for a solution to this problem.

bye,
Anderson Pereira Ataides

Em Terça 27 Agosto 2002 19:55, Stephen Lee escreveu:
> Hi,
>
> I am running a Foxpro application under Dosemu 1.1.3.2 (xdosemu) with
> the keyboard patches and things seem to be running smoothly. Problems
> occur when some users access the same Foxpro db files via Samba 2.2.4.
> Files locked under Dosemu/Foxpro are not locked when accessed by Samba.
> Some of the samba config settings include:
>
> kernel oplocks = yes
> locking = Yes
> oplocks = Yes
> level2 oplocks = Yes
> oplock contention limit = 2
> posix locking = Yes
> strict locking = No
>
> This is a Redhat 7.2 systems running kernel 2.4.18. What else do I need
> to configure to get Dosemu file locks recognized by Samba?
>
> Thanks,
> Stephen
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html