From: "Oscar A. Valdez" <oscar.valdez@plastipak.com.sv>
To: Stephen Lee <splee@plexio.com>
Cc: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: Samba and kernel oplocks - Smbmount
Date: 29 Aug 2002 08:39:48 -0600 [thread overview]
Message-ID: <1030631988.1163.11.camel@wzowski> (raw)
In-Reply-To: <1030595962.18043.97.camel@ralph.plexio.private>
I'm accessing Samba shares with Dosemu 1.0.2 and 1.0.2.1. File locking
works flawlessly and with simultaneous access by Window$ clients.
I mount the Samba share with
mount -t smbfs //SERVER/SHARE /mnt/MOUNTPOINT -o credentials=CREDENTIALS_FILE,workgroup=WORKGROUP,rw,gid=GID,fmask=770
and then, within Dosemu
lredir F: linux\fs/mnt/MOUNTPOINT
(Of course, all the stuff in capitals needs to be substituted correspondingly).
Works fine.
Oscar
El mié, 28-08-2002 a las 22:39, Stephen Lee escribió:
> On Tue, 2002-08-27 at 15:55, Stephen Lee wrote:
> > 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?
>
> Just for kicks, I tried to access the Foxpro db files via an smb share
> using smbmount. Instead of pointing $_hdimage to the Drdos/Foxpro
> directory directly, I pointed it to a directory mounted to the smb share
> containing the Drdos/Foxpro files. The idea was to make Dosemu use the
> Samba file locking system. Well...Dosemu runs and Foxpro starts but the
> whole process is REALLY slow. So slow that I didn't have the patience to
> test whether the file locking problem was fixed. It's not eating up cpu
> cycles either (according to top).
>
> Has anyone tried to access smb shares from Dosemu and if yes how did you
> do it?
>
> 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
prev parent reply other threads:[~2002-08-29 14:39 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 ` 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 [this message]
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=1030631988.1163.11.camel@wzowski \
--to=oscar.valdez@plastipak.com.sv \
--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