[28164] in Kerberos
Re: Client RPC timeout too short
daemon@ATHENA.MIT.EDU (Sam Hartman)
Tue Jul 31 18:42:11 2007
From: Sam Hartman <hartmans@mit.edu>
To: Mike Friedman <mikef@ack.berkeley.edu>
Date: Tue, 31 Jul 2007 18:41:50 -0400
In-Reply-To: <20070730162337.E67756@malcolm.berkeley.edu> (Mike Friedman's
message of "Mon, 30 Jul 2007 16:32:20 -0700 (PDT)")
Message-ID: <tslmyxcurf5.fsf@mit.edu>
MIME-Version: 1.0
Cc: kerberos@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
>>>>> "Mike" == Mike Friedman <mikef@ack.berkeley.edu> writes:
Mike> For years, I've been carrying around a mod to K5 that
Mike> increases the value of the RPC timeout from 25 to 180
Mike> seconds, to allow me to do a kadmin 'listprincs' without
Mike> timing out.
Mike> I wonder if MIT has any plans to incorporate the ability to
Mike> control this value (as a config option?) into the regular
Mike> distribution.
No, we have no current plans to do that. My main concern is detection
of failures. I guess we could potentially take such a mod for TCP
connections after the connection is already established.
It seems kind of unfortunate that the getprincs RPC is designed in
such a way that you need this mod.
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
