linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve Dickson <SteveD@redhat.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Adding the nfs4_use_min_auth module parameter
Date: Sat, 9 Nov 2013 13:04:44 +1100	[thread overview]
Message-ID: <20131109130444.2e0e9f73@notabene.brown> (raw)
In-Reply-To: <20131108101232.10d49851@tlielax.poochiereds.net>

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

On Fri, 8 Nov 2013 10:12:32 -0500 Jeff Layton <jlayton@redhat.com> wrote:


> Right, but we've defaulted to v4 for *years* now. Most people run statd
> and don't actually use it. No one seems to get bent out of shape about
> that though.

Given that statd can be started on demand by mount.nfs, this sounds like a
configuration error.


NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2013-11-09  2:04 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 19:09 [PATCH] Adding the nfs4_use_min_auth module parameter Steve Dickson
2013-11-07 19:25 ` Chuck Lever
2013-11-07 21:01   ` Jeff Layton
2013-11-07 21:40     ` Steve Dickson
2013-11-07 22:04       ` Jeff Layton
2013-11-07 21:35   ` Steve Dickson
2013-11-07 23:05     ` Chuck Lever
2013-11-08 12:41       ` Steve Dickson
2013-11-08 13:22         ` Jeff Layton
2013-11-08 15:00           ` Steve Dickson
2013-11-08 15:12             ` Jeff Layton
2013-11-08 16:10               ` Steve Dickson
2013-11-08 16:17                 ` J. Bruce Fields
2013-11-08 16:19                   ` Steve Dickson
2013-11-08 16:22                     ` J. Bruce Fields
2013-11-08 16:28                       ` Steve Dickson
2013-11-08 16:39                         ` J. Bruce Fields
2013-11-08 16:45                           ` Steve Dickson
2013-11-08 18:12                           ` Chuck Lever
2013-11-08 18:09                   ` Chuck Lever
2013-11-08 20:14                     ` J. Bruce Fields
2013-11-08 20:32                   ` Steve Dickson
2013-11-09  2:04               ` NeilBrown [this message]
2013-11-08 16:27             ` Weston Andros Adamson
2013-11-08 16:38               ` Steve Dickson
2013-11-08 15:04           ` J. Bruce Fields
2013-11-08 15:54             ` Chuck Lever
2013-11-08 16:14               ` J. Bruce Fields
2013-11-08 17:58                 ` Chuck Lever
2013-11-08 18:46                   ` Chuck Lever
2013-11-08 21:09                     ` J. Bruce Fields
2013-11-08 16:17               ` Steve Dickson
2013-11-08 15:46         ` Chuck Lever
2013-11-08 21:25           ` Steve Dickson
2013-11-07 19:26 ` Myklebust, Trond
2013-11-07 21:25   ` Steve Dickson
2013-11-07 21:39     ` Myklebust, Trond
2013-11-07 21:57       ` Steve Dickson
2013-11-07 22:29         ` Myklebust, Trond
2013-11-08 12:21           ` Steve Dickson
2013-11-08 14:30             ` Myklebust, Trond
2013-11-08 15:08               ` Steve Dickson
2013-11-08 15:16                 ` Myklebust, Trond
2013-11-08 16:31                   ` Steve Dickson

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=20131109130444.2e0e9f73@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@redhat.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 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).