From: Steve Dickson <SteveD@redhat.com>
To: Jeff Layton <jlayton@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsdcltrack: fix some minor nits in the manpage
Date: Fri, 19 Sep 2014 10:42:31 -0400 [thread overview]
Message-ID: <541C40D7.7070101@RedHat.com> (raw)
In-Reply-To: <1410790397-20511-1-git-send-email-jlayton@primarydata.com>
On 09/15/2014 10:13 AM, Jeff Layton wrote:
> nfsdcltrack isn't a daemon, and we should make mention of the section
> in RFC5661.
>
> Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Committed...
steved.
> ---
> utils/nfsdcltrack/nfsdcltrack.man | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/utils/nfsdcltrack/nfsdcltrack.man b/utils/nfsdcltrack/nfsdcltrack.man
> index 69407889df8a..c37c9a8d5813 100644
> --- a/utils/nfsdcltrack/nfsdcltrack.man
> +++ b/utils/nfsdcltrack/nfsdcltrack.man
> @@ -23,12 +23,13 @@ nfsdcltrack [\-d] [\-f] [\-s stable storage dir] <command> <args...>
> .SH "DESCRIPTION"
> .IX Header "DESCRIPTION"
> nfsdcltack is the NFSv4 client tracking callout program. It is not necessary
> -to install this daemon on machines that are not acting as NFSv4 servers.
> +to install this program on machines that are not acting as NFSv4 servers.
> .PP
> When a network partition is combined with a server reboot, there are
> edge conditions that can cause the server to grant lock reclaims when
> other clients have taken conflicting locks in the interim. A more detailed
> -explanation of this issue is described in \s-1RFC\s0 3530, section 8.6.3.
> +explanation of this issue is described in \s-1RFC\s0 3530, section 8.6.3
> +and in \s-1RFC\s0 5661, section 8.4.3.
> .PP
> In order to prevent these problems, the server must track a small amount
> of per-client information on stable storage. This program provides the
>
prev parent reply other threads:[~2014-09-19 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 14:13 [PATCH] nfsdcltrack: fix some minor nits in the manpage Jeff Layton
2014-09-19 14:42 ` Steve Dickson [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=541C40D7.7070101@RedHat.com \
--to=steved@redhat.com \
--cc=jlayton@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
/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.