From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: steved@redhat.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] gssd: cut down log chatter in gssd_search_krb5_keytab
Date: Thu, 7 Nov 2013 07:58:37 -0800 [thread overview]
Message-ID: <20131107155837.GA16658@infradead.org> (raw)
In-Reply-To: <1383839253-8223-1-git-send-email-jlayton@redhat.com>
On Thu, Nov 07, 2013 at 10:47:33AM -0500, Jeff Layton wrote:
> Because the kernel now looks for krb5 creds by default when mounting, we
> need to always have clients run rpc.gssd to avoid the 15s hang on the
> first mount attempt.
Not sure if it's the same hangs, but I see about the same length of a
hang on my Debian wheezy systems when accessing the first file for a
data operation, with rpc.gssd running or not. Funnily enough this also
happens when trying to read a non-existand file, but not for things like
a simple readdir.
Still looking into it, but being a non-interruptible sleep it's fairly
annoying.
That being said Debian wheezy also only starts rpc.gssd from the init
scripts if it sees a krb option in /etc/fstab, which I don't have.
next prev parent reply other threads:[~2013-11-07 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 15:47 [PATCH] gssd: cut down log chatter in gssd_search_krb5_keytab Jeff Layton
2013-11-07 15:58 ` Christoph Hellwig [this message]
2013-11-07 16:09 ` Jeff Layton
2013-11-07 16:21 ` Christoph Hellwig
2013-11-07 16:33 ` Jeff Layton
2013-11-07 16:35 ` Christoph Hellwig
2013-11-07 16:36 ` Jeff Layton
2013-11-07 16:38 ` Christoph Hellwig
2013-11-07 16:47 ` Steve Dickson
2013-11-07 16:56 ` Jeff Layton
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=20131107155837.GA16658@infradead.org \
--to=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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 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.