From: Claudia Neumann <dr.claudia.neumann@gmx.de>
To: dosEmu-list <linux-msdos@vger.kernel.org>
Subject: Re: cifs 1.50 and dosemu 1.4 great combination
Date: Wed, 14 Nov 2007 17:03:01 +0100 [thread overview]
Message-ID: <200711141703.01836.dr.claudia.neumann@gmx.de> (raw)
In-Reply-To: <70AFCDD624131E4F8E093DF91AA2CBA225B2BC@SERVER.STOKE01.local>
Hi Tarquin!
Am Mittwoch, 14. November 2007 15:39 schrieb Tarquin Adams:
> However, when I run sessions with these different usernames accessing the
> CIFS mounted directory lredir'd in dosemu I get Btrieve error 14 (pre-image
> open error) when the software tries to access the data files. This is
> related to the .pre files that Btrieve creates and it appears a .pre file
> created by one user cannot be accessed by another, which is essential!
I can't tell anything about using different users accessing a share. There you
have to look at the samba docs.
> Does anyone have any advice or recommended settings for enabling whatever
> oplock or other locking mechanism is required for this to work correctly?
> I notice several posts which say they have got record locking working
> using CIFS with SAMBA but no-one gives specifc smb.conf or CIFS settings
> for this.
The locking is correct at least with my application (Clipper,xbase) with cifs
> 1.45 and samba >= 3.0.25b.
The parameter in the smb.conf is
strict locking = yes
most of the other locking parameters are ignored with cifs.
HTH
Claudia
next prev parent reply other threads:[~2007-11-14 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 14:39 cifs 1.50 and dosemu 1.4 great combination Tarquin Adams
2007-11-14 16:03 ` Claudia Neumann [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-15 10:26 Tarquin Adams
2007-11-21 4:04 ` kemas
2007-10-11 14:30 kemas
[not found] ` <470E52D1.5040406@pobox.com>
[not found] ` <1192159242.2490.10.camel@localhost>
2007-10-12 5:31 ` Alain M.
2007-10-12 6:19 ` Bart Oldeman
2007-10-12 11:58 ` Claudia Neumann
2007-10-15 3:23 ` kemas
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=200711141703.01836.dr.claudia.neumann@gmx.de \
--to=dr.claudia.neumann@gmx.de \
--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