From: Christian Reis <kiko@async.com.br>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: NFS@lists.sourceforge.net, Guilherme Salgado <salgado@async.com.br>
Subject: Re: Stale fcntl lock never released
Date: Tue, 24 Jun 2003 16:07:23 -0300 [thread overview]
Message-ID: <20030624190723.GF3168@async.com.br> (raw)
In-Reply-To: <shshe6fti31.fsf@charged.uio.no>
On Tue, Jun 24, 2003 at 09:02:10PM +0200, Trond Myklebust wrote:
> >>>>> " " == Christian Reis <kiko@async.com.br> writes:
>
> > (Trond, do any of the lockd patches in
> > http://www.fys.uio.no/~trondmy/src/2.4.21/ fix something like
> > this?)
>
> No. This is what rpc.statd is supposed to do. When a client reboots,
> it is supposed to notify the server that it should remove all locks
> belonging to that client.
What if the client never reboots, but instead is turned off and another
client turned on? Should the lock persist? For how long?
Take care,
--
Christian Reis, Senior Engineer, Async Open Source, Brazil.
http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-06-24 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 22:14 Stale fcntl lock never released Christian Reis
2003-06-24 19:02 ` Trond Myklebust
2003-06-24 19:07 ` Christian Reis [this message]
2003-06-24 19:14 ` Trond Myklebust
2003-06-24 19:18 ` Christian Reis
2003-06-24 21:28 ` Steve Dickson
2003-06-24 22:03 ` Spencer Shepler
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=20030624190723.GF3168@async.com.br \
--to=kiko@async.com.br \
--cc=NFS@lists.sourceforge.net \
--cc=salgado@async.com.br \
--cc=trond.myklebust@fys.uio.no \
/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.