From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michael Guntsche <mike@it-loops.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Kerberos auth Problem with nfs3/4
Date: Tue, 3 Aug 2010 19:14:19 -0400 [thread overview]
Message-ID: <20100803231419.GC9752@fieldses.org> (raw)
In-Reply-To: <20100803222002.GA1741@marvin.comsick.at>
On Wed, Aug 04, 2010 at 12:20:02AM +0200, Michael Guntsche wrote:
> gibson being the server and zaphod being the client here. As you said
> the server tries to connect back to the client which fails since
> rpc.svcgssd is not running on the client. Should the server try to
> connect back to the client this way in the first place and if yes
> shouldn't he stop trying after seeing that it is not working?
What I'd expect would be for it to make one try with each new client and
then give up. (But actually if the client doesn't renew state while
files aren't open--it may also end up retrying if the client's idle for
a minute or so.) If it's retrying more often than that, that's a
problem.
In any case we should probably reconsider how that message is generated,
to prevent it going to the log by default in this case.
--b.
next prev parent reply other threads:[~2010-08-03 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:45 Kerberos auth Problem with nfs3/4 Michael Guntsche
2010-08-03 19:43 ` J. Bruce Fields
2010-08-03 20:13 ` Michael Guntsche
2010-08-03 21:19 ` Michael Guntsche
2010-08-03 21:36 ` J. Bruce Fields
2010-08-03 21:55 ` Michael Guntsche
2010-08-03 23:16 ` J. Bruce Fields
2010-08-04 5:29 ` Michael Guntsche
2010-08-03 22:20 ` Michael Guntsche
2010-08-03 23:14 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-03 16:27 Michael Guntsche
2010-08-03 19:03 Michael Guntsche
2010-08-03 20:07 ` Andy Adamson
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=20100803231419.GC9752@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mike@it-loops.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.