From: "Gustavo Sverzut Barbieri" <gsbarbieri@yahoo.com.br>
To: linux-msdos@vger.kernel.org
Subject: Clipper 5.2 app with multiples accesses to DBF
Date: Tue, 22 Jul 2003 16:18:31 -0300 (ART) [thread overview]
Message-ID: <20030722191831.68191.qmail@web20902.mail.yahoo.com> (raw)
Hello,
I'm trying to replace M$-Windows in my parent's lab with GNU/Linux. He
needs a Clipper-CA 5.2 software to run there, but I have some problems.
I run this way:
* I have a SAMBA server wich exports my files (DBF);
* I have 2 clients still running M$ Windows. If they try to access the
same file, everything works as expected, no problems;
* I have 1 GNU/Linux client wich mounts the SMB share and I have a
symbolic link from it to dosemu dir (~/.dosemu/drives/c/MYDIR ->
/mnt/SMB_EXPORTED_DIR). When I access a file (dbf) with this machine
with any other client (Windows or Linux) I got error messages and
inconsistence (sometimes I don't get the error, but the written data is
lost).
PS: I'm using dosemu-devel (unstable)
The same problems occurs if instead of the SMB mounted share I use NFS
or a local file (running dosemu in the server)
So, the problem seems to be in file locking in dosemu... Searching the
net I've found people with problems regarding M$-Dos record-locking. I
think that's my problem too... unfortunately I didn't found any
solution.
So, there is a way to use multiple dosemu to concurrently access the
same file?
Thanks!
Gustavo
_______________________________________________________________________
Yahoo! Mail
Mais espaço, mais segurança e gratuito: caixa postal de 6MB, antivírus, proteção contra spam.
http://br.mail.yahoo.com/
-
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
reply other threads:[~2003-07-22 19:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030722191831.68191.qmail@web20902.mail.yahoo.com \
--to=gsbarbieri@yahoo.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