From: Spencer Shepler <spencer.shepler@sun.com>
To: Christian Reis <kiko@async.com.br>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
NFS@lists.sourceforge.net,
Guilherme Salgado <salgado@async.com.br>
Subject: Re: Stale fcntl lock never released
Date: Tue, 24 Jun 2003 15:03:10 -0700 [thread overview]
Message-ID: <3EF8CA9E.FB84DEEF@sun.com> (raw)
In-Reply-To: 20030624191830.GG3168@async.com.br
Some server implementations provide a administrative command
to release NFS locks held at the server for a specific client
for this scenario where the client is turned off or will never
contact the server again.
Spencer
Christian Reis wrote:
>
> On Tue, Jun 24, 2003 at 09:14:10PM +0200, Trond Myklebust wrote:
> > >>>>> " " == Christian Reis <kiko@async.com.br> writes:
> >
> > > What if the client never reboots, but instead is turned off and
> > > another client turned on? Should the lock persist? For how
> > > long?
> >
> > It will persist forever.
>
> How odd.
>
> Is the only solution is to restart the server-side statd, or knfsd?
>
> 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
-------------------------------------------------------
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
prev parent reply other threads:[~2003-06-24 22:03 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
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 [this message]
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=3EF8CA9E.FB84DEEF@sun.com \
--to=spencer.shepler@sun.com \
--cc=NFS@lists.sourceforge.net \
--cc=kiko@async.com.br \
--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.