From: Uwe Feldtmann <uwe@microshare.com.au>
To: Stephen Lee <splee@plexio.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Samba and kernel oplocks - Solved????
Date: 11 Sep 2002 18:58:56 +1000 [thread overview]
Message-ID: <1031734736.2454.30.camel@eeyore> (raw)
In-Reply-To: <1031008087.27013.111.camel@ralph.plexio.private>
Hi,
I've been following this thread in the hope that it would help with a
similar problem that I've been experiencing. Alas it doesn't help.
The scenario:
I am running a dos app from a shared samba directory on a linux server
with both windows and dosemu clients.
The problem:
When the dosemu clients start the app first, the windows clients get the
following message:-
Cannot access the file "N:\DATA\EQUITY\EQUITY.EXE".
Make sure the file is a valid program and that it is not in use by
another program.
When the windows clients start the app first, the dosemu clients don't
have a problem accessing the program or the data.
I've applied the patch to dosemu from the previous posts on this thread
with to dosemu 1.1.3 and am using the current version of samba.
EQUITY.EXE is a clarion 2.1 based dos app that has been in use for years
on all networks tested.
Any ideas?
Yours,
Uwe.
On Tue, 2002-09-03 at 09:08, Stephen Lee wrote:
> On Wed, 2002-08-28 at 23:21, Sergey Suleymanov wrote:
> > >>>>> Anderson Pereira Ataides writes:
> >
> > Anderson> I thing problem is not only samba because nfs also have
> > Anderson> problem. I have two Linux workstations and when I lock
> > Anderson> record in one of them, the other one can't see this lock.
> >
> > Anderson> Like you I'm waiting for a solution to this problem.
> >
> > Well, I'm just try locks with samba, and it seems work.
> > oplocks = no in smb.conf and this hack to mfs.c
> >
> > --- src/dosext/mfs/mfs.c.orig Thu Aug 29 10:09:33 2002
> > +++ src/dosext/mfs/mfs.c Thu Aug 29 10:08:31 2002
> > @@ -3823,11 +3823,16 @@
> > the top two bits are set. Shift the top ones by two bits. This
> > still allows OLE2 apps to operate, but should stop lockd from
> > dieing */
> > +#if 0
> > if ((larg.l_start & mask) != 0)
> > larg.l_start = (larg.l_start & ~mask) | ((larg.l_start & mask) >> 2);
> > +#else
> > + larg.l_start &= 0x7fffffff;
> > +#endif
> > ret = fcntl (fd,F_SETLK,&larg);
> > Debug0((dbg_fd, "lock fd=%x rc=%x type=%x whence=%x start=%lx, len=%lx\n",
> > fd, ret, larg.l_type, larg.l_whence, larg.l_start,larg.l_len));
> > + if (ret == -1) SETWORD(&(state->eax), ACCESS_DENIED);
> > return ret != -1 ? TRUE : FALSE;
> > }
> > break;
> >
> > I don't understand that bit magic, maybe this won't work with
> > nfs or something else.
> >
>
> I'm happy to say that the above patch allows Foxpro/Dosemu file locks to
> be recognized by Samba 2.2.4. This means I can run the Foxpro
> application via Dosemu and under MSDOS/Win98/Samba simultaneously! The
> only issue I had with the above patch is that the line numbers did not
> match my version of Dosemu 1.1.3.2 with keyboard patches. I had to
> insert the lines manually.
>
> Now onto stress testing to ensure the changes do not affect Dosemu
> stability.
>
> Thanks Sergey!
>
> 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
>
next prev parent reply other threads:[~2002-09-11 8:58 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
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 ` Uwe Feldtmann [this message]
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=1031734736.2454.30.camel@eeyore \
--to=uwe@microshare.com.au \
--cc=linux-msdos@vger.kernel.org \
--cc=splee@plexio.com \
/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