From: "Gregor Ibic" <gregor.ibic@intelicom.si>
To: Bart Oldeman <oldeman@math.ohio-state.edu>
Cc: Lista dosemu <linux-msdos@vger.kernel.org>
Subject: RE: [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again))
Date: Mon, 10 Feb 2003 20:04:30 +0100 [thread overview]
Message-ID: <FMEOJDPGJGFFCKLPLAPLMEAKGGAA.gregor.ibic@intelicom.si> (raw)
In-Reply-To: <Pine.LNX.4.33.0302101354170.5898-100000@DHCP-94-246.math.ohio-state.edu>
Wrong is that DOSEMU client cant read the file. Win client lock it properly
but dosemu probably cant read properly the lock information and pass it to
the client. The app is written in C (normal file locking).
lsof for the file does not say anything when win client opens it
only when dosemu client opens it (like I sent it before)
Regards,
Gregor
next prev parent reply other threads:[~2003-02-10 19:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.4.44.0302050103010.25172-100000@math.ohio-state.edu>
2003-02-05 6:40 ` dosemu and CLIPPER locks (again) (fwd) Bart Oldeman
2003-02-05 12:24 ` Anderson Pereira Ataides
2003-02-06 6:56 ` [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again)) Bart Oldeman
2003-02-07 12:06 ` Michal Samek
2003-02-10 15:42 ` Gregor Ibic
2003-02-10 18:07 ` Bart Oldeman
2003-02-10 18:45 ` Gregor Ibic
2003-02-10 18:57 ` Bart Oldeman
2003-02-10 19:04 ` Gregor Ibic [this message]
2003-02-10 19:14 ` Bart Oldeman
2003-02-10 19:36 ` Gregor Ibic
2003-02-10 19:49 ` Bart Oldeman
2003-02-10 20:00 ` Gregor Ibic
2003-02-10 20:06 ` Bart Oldeman
2003-02-11 8:37 ` Sergey Suleymanov
2003-02-11 17:11 ` Bart Oldeman
2003-02-10 21:28 ` WARNING: smbfs and locking (was RE: [PATCH] (locking) (was Re: dosemu and CLIPPER locks (again)))) Bart Oldeman
2003-02-10 23:17 ` WARNING: smbfs and locking -- POSIX v. CIFS locking, and how DOS doesn't do CIFS locking (bad things man) Bryan J. Smith
2003-02-11 0:31 ` Bart Oldeman
2003-02-11 13:00 ` WARNING: smbfs and locking -- Mega-oversimplification Bryan J. Smith
2003-02-11 12:07 ` WARNING: smbfs and locking Anderson Pereira Ataides
2003-02-11 13:01 ` Reinhard Karcher
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=FMEOJDPGJGFFCKLPLAPLMEAKGGAA.gregor.ibic@intelicom.si \
--to=gregor.ibic@intelicom.si \
--cc=linux-msdos@vger.kernel.org \
--cc=oldeman@math.ohio-state.edu \
/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