From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P and locking
Date: Tue, 31 Oct 2006 15:16:28 +0000 [thread overview]
Message-ID: <001a50a78f873e5868ec3fd72944686a@terzarima.net> (raw)
In-Reply-To: <775b8d190610310644w822038frdc204969ed924ea@mail.gmail.com>
>> > So far my plan to extend is to have messages mimicking fcntl, but
>> > maybe that's not the best way to get it done. Did anyone work on
>> > locking and would like to share their experience or opinion?
in commercial unix database work i never found the in-built fcntl or record locking
particularly useful and did my own. it was the usual `both too much
and too little' with the system's attempt, and thus i found it fairly pointless.
i wrote up something about it at the time but sadly that was years before
the dumps started.
next prev parent reply other threads:[~2006-10-31 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3190d0e50610250505j723f392fp319da7ff20adc313@mail.gmail.com>
2006-10-31 14:25 ` Alejo Sanchez
2006-10-31 14:36 ` Bruce Ellis
2006-10-31 14:39 ` Anel Philippe
2006-10-31 14:44 ` Bruce Ellis
2006-10-31 15:16 ` Charles Forsyth [this message]
2006-10-31 16:09 ` Bruce Ellis
2006-10-31 16:11 ` Alejo Sanchez
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=001a50a78f873e5868ec3fd72944686a@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.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;
as well as URLs for NNTP newsgroup(s).