From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] mount.nfs: Update description of clientaddr= in nfs(5)
Date: Thu, 30 Aug 2007 17:37:16 -0400 [thread overview]
Message-ID: <20070830213716.GE10808@fieldses.org> (raw)
In-Reply-To: <20070830194810.4524.58037.stgit@monet.1015granger.net>
On Thu, Aug 30, 2007 at 03:48:10PM -0400, Chuck Lever wrote:
> +Specifies a single IPv4 address in dotted-quad form that the
> +NFS client should advertise to a server for performing NFSv4
> +callback requests for this mount point.
> +If not specified, the mount command attempts to discover an
> +appropriate callback address, then passes it to the NFS client.
> +However, in the presence of multiple client network interfaces,
> +special routing policies, or atypical network topologies, the
> +exact address to use for callbacks may be difficult for the
> +mount command to determine automatically.
Sounds good to me!
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-30 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 19:48 [PATCH] mount.nfs: Update description of clientaddr= in nfs(5) Chuck Lever
2007-08-30 21:37 ` J. Bruce Fields [this message]
2007-08-31 0:12 ` Gabriel Barazer
2007-08-31 13:54 ` Chuck Lever
2007-08-31 1:35 ` Talpey, Thomas
2007-08-31 13:56 ` Chuck Lever
-- strict thread matches above, loose matches on Subject: below --
2007-08-31 15:15 Chuck Lever
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=20070830213716.GE10808@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox