From: Jeff Layton <jlayton@redhat.com>
To: Steve Dickson <SteveD@redhat.com>
Cc: Andy Adamson <androsadamson@gmail.com>,
"Adamson, Andy" <William.Adamson@netapp.com>,
"Myklebust, Trond" <Trond.Myklebust@netapp.com>,
"<linux-nfs@vger.kernel.org>" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/1] SUNRPC handle EKEYEXPIRED in call_refreshresult
Date: Sat, 30 Jun 2012 07:00:36 -0400 [thread overview]
Message-ID: <20120630070036.232946cb@tlielax.poochiereds.net> (raw)
In-Reply-To: <4FEE1381.1000209@RedHat.com>
On Fri, 29 Jun 2012 16:43:45 -0400
Steve Dickson <SteveD@redhat.com> wrote:
> >>>
> >>
> >> Easy to say, far more difficult to do.
> >
> > Here is how simple it is.
> >
> > $ kinit
> > $ krenew -K 30&
> If this simple process cannot renew a ticket then its a bug
> in the client... We have to let processes like this to renew
> renewable tickets!
>
> I've never been a fan of this hang from the beginning but
> if its getting in the way of things renewing tickets then its
> got to go... IMHO...
>
> Lets push the error up to the app and then educate people
> on how to avoid the error...
>
Fair enough. I'd prefer to see this handled better too. If Andy has a
solution for the writeback issues then I'm fine with reverting this
behavior.
If we have kerberized NFS howtos anywhere (do we?) then we probably
need to add some notes about krenewd or how to make sssd handle this.
--
Jeff Layton <jlayton@redhat.com>
prev parent reply other threads:[~2012-06-30 11:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 20:05 [PATCH 0/1] SUNRPC handle EKEYEXPIRED in call_refreshresult andros
2012-06-27 20:05 ` [PATCH 1/1] " andros
2012-07-16 18:44 ` Myklebust, Trond
2012-07-16 20:09 ` Adamson, Andy
2012-06-28 15:43 ` [PATCH 0/1] " Jeff Layton
2012-06-28 16:31 ` Adamson, Andy
2012-06-28 18:03 ` Jeff Layton
2012-06-28 23:33 ` Andy Adamson
2012-06-29 20:43 ` Steve Dickson
2012-06-30 11:00 ` Jeff Layton [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=20120630070036.232946cb@tlielax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=SteveD@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=William.Adamson@netapp.com \
--cc=androsadamson@gmail.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 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.