From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Ara.T.Howard" <Ara.T.Howard@noaa.gov>
Cc: nfs@lists.sourceforge.net
Subject: Re: locking bug
Date: Fri, 10 Dec 2004 17:05:48 -0500 [thread overview]
Message-ID: <20041210220548.GH9291@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.60.0412101428350.21479@harp.ngdc.noaa.gov>
On Fri, Dec 10, 2004 at 02:34:32PM -0700, Ara.T.Howard wrote:
> summary:
>
> * process on host 0 opens file, locks it, and read it in using separate
> file
> handle. it then sleeps holding lock.
>
> * process on host 1 attempting the exact same sequence (and so expecting
> to
> find the file locked) is able to obtain the lock.
>
> * if the file is not slurped this code acts as it's supposed to - process
> on
> host 1 cannot obtain lock
>
>
> is this known? if not should i report here or to redhat?
You understand that the close releases the lock? From "man fcntl":
"As well as being removed by an explicit F_UNLCK, record locks are auto-
matically released when the process terminates or if it closes any file
descriptor referring to a file on which locks are held."
--b.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-12-10 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 21:34 locking bug Ara.T.Howard
2004-12-10 22:05 ` J. Bruce Fields [this message]
2004-12-10 22:15 ` Ara.T.Howard
-- strict thread matches above, loose matches on Subject: below --
2006-05-02 7:42 Robert F. Merrill
2006-05-02 9:59 ` locking bug Jiri Slaby
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=20041210220548.GH9291@fieldses.org \
--to=bfields@fieldses.org \
--cc=Ara.T.Howard@noaa.gov \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.