From: Steve Dickson <SteveD@redhat.com>
To: "Myklebust, Trond" <Trond.Myklebust@netapp.com>
Cc: Simo Sorce <simo@redhat.com>,
Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 2/3] Avoid reverse resolution for server name
Date: Tue, 02 Apr 2013 15:20:45 -0400 [thread overview]
Message-ID: <515B2F8D.3030302@RedHat.com> (raw)
In-Reply-To: <4FA345DA4F4AE44899BD2B03EEEC2FA9286FB37F@SACEXCMBX04-PRD.hq.netapp.com>
On 02/04/13 13:58, Myklebust, Trond wrote:
>> -----Original Message-----
>> From: linux-nfs-owner@vger.kernel.org [mailto:linux-nfs-
>> owner@vger.kernel.org] On Behalf Of Simo Sorce
>> Sent: Tuesday, April 02, 2013 1:49 PM
>> To: Linux NFS Mailing list
>> Subject: [PATCH 2/3] Avoid reverse resolution for server name
>>
>> A NFS client should be able to work properly even if the DNS Reverse record
>> for the server is not set. There is no excuse to forcefully prevent that from
>> working when it can.
>
> Note that rpc.statd has the same limitation.
>
>> This patch adds a new -N option that takes an 'on' or 'off' argument and
>> controls whether forced PTR resolution is avoided (on) or performed (off)
>
> '-N' already has a very different meaning on rpc.mountd and rpc.nfsd. It might therefore be better to choose a different name to avoid confusion.
> Also, why do a single option with an 'on/off' argument instead of just choosing 2 options ?
Do we really what two options? why not just have something like -Z that will restore today default?
steved.
>
> Trond
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-04-02 19:20 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 17:49 [PATCH 0/3] Avoid DNS Reverse lookups when possible Simo Sorce
2013-04-02 17:49 ` [PATCH 1/3] Fix segfault when using -R option Simo Sorce
2013-04-02 19:11 ` Steve Dickson
2013-04-02 17:49 ` [PATCH 2/3] Avoid reverse resolution for server name Simo Sorce
2013-04-02 17:58 ` Myklebust, Trond
2013-04-02 18:08 ` Simo Sorce
2013-04-02 18:53 ` Jeff Layton
2013-04-02 18:21 ` Simo Sorce
2013-04-02 18:25 ` Steve Dickson
2013-04-02 18:44 ` Simo Sorce
2013-04-02 19:20 ` Steve Dickson [this message]
2013-04-02 19:32 ` [PATCH 0/2] Alternative patchset to avoid PTR lookups Simo Sorce
2013-04-02 19:32 ` [PATCH 1/2] Avoid reverse resolution for server name Simo Sorce
2013-04-08 13:39 ` Steve Dickson
2013-04-08 14:08 ` Simo Sorce
2013-04-09 17:15 ` Steve Dickson
2013-04-09 17:25 ` Simo Sorce
2013-04-09 17:35 ` Steve Dickson
2013-04-09 18:02 ` Simo Sorce
2013-04-09 18:54 ` J. Bruce Fields
2013-04-09 19:12 ` Steve Dickson
2013-04-09 19:22 ` J. Bruce Fields
2013-04-10 10:43 ` Jeff Layton
2013-04-10 14:53 ` Steve Dickson
2013-04-02 19:32 ` [PATCH 2/2] Document new -z/-Z options Simo Sorce
2013-04-03 14:20 ` J. Bruce Fields
2013-04-03 14:35 ` Myklebust, Trond
2013-04-03 14:56 ` J. Bruce Fields
2013-04-03 15:10 ` Myklebust, Trond
2013-04-03 15:27 ` Myklebust, Trond
2013-04-02 17:49 ` [PATCH 3/3] Document new -N option Simo Sorce
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=515B2F8D.3030302@RedHat.com \
--to=steved@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=simo@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).