From: "J. Bruce Fields" <bfields@fieldses.org>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: [patch] lockd control of grace period for HA NFS
Date: Mon, 6 Dec 2004 10:04:28 -0500 [thread overview]
Message-ID: <20041206150428.GC20864@fieldses.org> (raw)
In-Reply-To: <OFB81726D4.627FD14C-ON88256F56.0010B138-88256F56.001402F0@us.ibm.com>
On Tue, Nov 23, 2004 at 07:38:34PM -0800, Marc Eshel wrote:
> 'echo 1 > /porc/sys/fs/nfs/nlm_grace' will put lockd in grace period and
> 'echo 0 > /porc/sys/fs/nfs/nlm_grace' will take it out of grace period but
> it is not necessary to 'echo 0' since it will just come out of grace period
> when the period ends.
The "echo 0" is a little dangerous, isn't it? Do we really need the
ability to end the grace period prematurely?--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-06 15:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16802.32693.974799.504191@cse.unsw.edu.au>
2004-11-24 3:38 ` [patch] lockd control of grace period for HA NFS Marc Eshel
2004-11-24 4:28 ` Trond Myklebust
2004-11-24 5:35 ` Marc Eshel
2004-11-24 16:21 ` Trond Myklebust
2004-11-24 23:49 ` Marc Eshel
2004-11-25 0:15 ` Trond Myklebust
2004-11-29 23:12 ` Marc Eshel
2004-11-30 15:55 ` William A.(Andy) Adamson
2004-11-30 17:03 ` Marc Eshel
2004-12-01 17:17 ` Calum Mackay
2004-12-01 20:58 ` William A.(Andy) Adamson
2004-12-06 15:04 ` J. Bruce Fields [this message]
2004-12-06 18:20 ` Marc Eshel
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=20041206150428.GC20864@fieldses.org \
--to=bfields@fieldses.org \
--cc=eshel@almaden.ibm.com \
--cc=neilb@cse.unsw.edu.au \
--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.