From: Sven Geggus <lists@fuchsschwanzdomain.de>
To: linux-nfs@vger.kernel.org
Subject: Re: NFS4+KRB5 trouble in Kernel >3.8
Date: Fri, 7 Jun 2013 15:41:21 +0000 (UTC) [thread overview]
Message-ID: <kosuv1$gjp$1@ultimate100.geggus.net> (raw)
In-Reply-To: CEF420B2-F649-40F6-B0D7-2187996A5493@oracle.com
Chuck Lever <chuck.lever@oracle.com> wrote:
> Your complaint was about mount problems, so I assumed client side,
> and did not visit the link you provided.
My Problem is almost certainly a server Problem. I will see what I
can find with tcpdump/wireshark on monday.
Sven
--
"Dynamische IP-Nummern sind Security-Homöopathie."
(Kristian Köhntopp)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
prev parent reply other threads:[~2013-06-07 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 13:24 NFS4+KRB5 trouble in Kernel >3.8 Sven Geggus
2013-06-06 14:48 ` Chuck Lever
2013-06-07 10:19 ` Sven Geggus
2013-06-07 14:51 ` Chuck Lever
2013-06-07 15:41 ` Sven Geggus [this message]
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='kosuv1$gjp$1@ultimate100.geggus.net' \
--to=lists@fuchsschwanzdomain.de \
--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 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.