From: Stephen Lee <splee@plexio.com>
To: Anderson Pereira Ataides <anderson.pa@persogo.com.br>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: Samba and kernel oplocks
Date: 28 Aug 2002 15:30:20 -0700 [thread overview]
Message-ID: <1030573821.18055.73.camel@ralph.plexio.private> (raw)
In-Reply-To: <02082810141600.00982@anderson.cdc.net>
On Wed, 2002-08-28 at 06:14, Anderson Pereira Ataides wrote:
> 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
The patch sent by Bart did not work in my case either. I wonder if this
problem was introduced in the 1.1.3 branch or also exists in the 1.0.2
stable series as well?
Stephen
next prev parent reply other threads:[~2002-08-28 22:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 22:55 Samba and kernel oplocks Stephen Lee
2002-08-28 13:14 ` Anderson Pereira Ataides
2002-08-28 22:30 ` Stephen Lee [this message]
2002-08-29 6:21 ` Sergey Suleymanov
2002-08-29 6:56 ` Stephen Lee
2002-08-29 7:18 ` Sergey Suleymanov
2002-08-29 17:21 ` Stephen Lee
2002-08-29 17:28 ` Bart Oldeman
2002-08-29 17:57 ` Stephen Lee
2002-09-02 23:08 ` Samba and kernel oplocks - Solved Stephen Lee
2002-09-11 8:58 ` Samba and kernel oplocks - Solved???? Uwe Feldtmann
2002-08-29 4:39 ` Samba and kernel oplocks - Smbmount Stephen Lee
2002-08-29 14:39 ` Oscar A. Valdez
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1030573821.18055.73.camel@ralph.plexio.private \
--to=splee@plexio.com \
--cc=anderson.pa@persogo.com.br \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox