From: Mikhail Kruk <meshko@cs.brandeis.edu>
To: David Schwartz <davids@webmaster.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: fcntl file locking and pthreads
Date: Sun, 4 May 2003 17:50:49 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0305041741390.1510-100000@iole.cs.brandeis.edu> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKMEIFCLAA.davids@webmaster.com>
> > Two reference platforms for
> > threads are Solaris and Windows. I don't know how Solaris handles this,
> > but on Windows file locks are per thread, not per process.
>
> Surely your argument isn't that UNIX should do things a certain way because
> that's how Windows does it? We can talk about two things, how things are and
> how they should be. This discussion seemed to be about how things should be.
I mentioned Windows because it happens to have a very mature threading
implementation and I don't see why Unix can't look at something from
Windows as a reference.
Anyway, I understand your argument about thread vs processes resources. I
also checked that it works the same way on Solaris (which of course is a
better reference point for Linux), so I agree that fcntl behavior is ok.
Thanks for your explanation!
next prev parent reply other threads:[~2003-05-04 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 6:13 fcntl file locking and pthreads Mikhail Kruk
2003-05-04 12:58 ` Jamie Lokier
2003-05-04 13:25 ` Mikhail Kruk
2003-05-04 15:24 ` Miquel van Smoorenburg
2003-05-04 18:40 ` David Schwartz
2003-05-04 19:29 ` Mikhail Kruk
2003-05-04 20:55 ` David Schwartz
2003-05-04 21:50 ` Mikhail Kruk [this message]
2003-05-04 21:29 ` Mark Mielke
2003-05-04 21:56 Ville Voutilainen
2003-05-04 22:04 ` Mikhail Kruk
2003-05-04 22:29 Ville Voutilainen
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=Pine.LNX.4.33.0305041741390.1510-100000@iole.cs.brandeis.edu \
--to=meshko@cs.brandeis.edu \
--cc=davids@webmaster.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).