Return-Path: Received: from caiajhbihbdd.dreamhost.com ([208.97.187.133]:49352 "EHLO webmail5.g.dreamhost.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1760384AbZJMQAH (ORCPT ); Tue, 13 Oct 2009 12:00:07 -0400 Message-ID: <08395e6249442278ab2b59c2ae4cfd14.squirrel@webmail.rainiday.com> In-Reply-To: <20091013114441.2882c8b9@tlielax.poochiereds.net> References: <20091009121602.5ec86dfb@tlielax.poochiereds.net> <1c358fde92c49215d84129a1bfe2c6ec.squirrel@webmail.rainiday.com> <20091010090039.4dfd1dfb@tlielax.poochiereds.net> <20091013114441.2882c8b9@tlielax.poochiereds.net> Date: Tue, 13 Oct 2009 08:59:29 -0700 Subject: Re: [NFS] NFS/krb and batch jobs - doable? From: raini@rainiday.com To: "Jeff Layton" Cc: linux-nfs@vger.kernel.org, "Kevin Coffman" Content-Type: text/plain; charset=US-ASCII Sender: linux-nfs-owner@vger.kernel.org List-ID: MIME-Version: 1.0 > You and Kevin are correct. rpc.gssd only looks at the mtime. When I did > the work to allow the CIFS SPNGEO upcall to find alternate credcaches, > I implemented the behavior I described (prefer the latest TGT > expiration) -- sorry for the confusion... > > It probably wouldn't be too hard to change rpc.gssd to prefer > credcaches with the latest TGT expiration if it was considered a > desirable change. > > Kevin, any thoughts? This would be a big plus from me - I still wouldn't be able to create per-job ccaches of course, but if a user who knew they needed to run a job could create a long lifetime renewable ticket in /tmp/krb5cc__batch, say, and NFS would use this in preference to a later login ticket, this would really help.