Received: from arioch.imrryr.org (arioch.imrryr.org [38.117.134.205]) by krbdev.mit.edu (8.12.9) with ESMTP id l3DFRvL8027430; Fri, 13 Apr 2007 11:27:57 -0400 (EDT)
Received: from imrryr.org (localhost [127.0.0.1]) by arioch.imrryr.org (Postfix) with ESMTP id 2D61537339 for <rt-comment@krbdev.mit.edu>; Fri, 13 Apr 2007 11:25:13 -0400 (EDT)
To: rt-comment@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #5440] sendto_kdc() not signal safe, doesn't respond well to staggered TCP responses. 
In-Reply-To: Your message of "Fri, 13 Apr 2007 03:20:21 EDT." <rt-5440-23520.17.2671333596269@krbdev.mit.edu> 
Organization: The Fall of Imrryr
User-Agent: nmh-1.0.4 (NetBSD/alpha)
X-Copyright: Copyright 2005, R. C. Dowdeswell. All Rights Reserved.
X-Window-System: Release 6.3
Date: Fri, 13 Apr 2007 11:25:13 -0400
From: Roland Dowdeswell <elric@imrryr.org>
Message-ID: <20070413152513.2D61537339@arioch.imrryr.org>
RT-Send-Cc: 
X-RT-Original-Encoding: iso-8859-1
Content-Length: 670

On 1176448821 seconds since the Beginning of the UNIX epoch
"Ken Raeburn via RT" wrote:
>

>After a little testing with a hacked KDC that sends back TCP responses in piec
>es with delays, I 
>don't think that there is a problem with that part of the client code.
>
>The library changes I've just checked in appear to fix the select/EINTR proble
>m, so I'm going to 
>mark this ticket as resolved.

Yeah, I think that I was a little aggressive in the scope of the
problem.  It wasn't signal safe but on the TCP staggering, I didn't
notice a different bit of code that dealt with that.

Thanks,

--
    Roland Dowdeswell                      http://www.Imrryr.ORG/~elric/