MIME-Version: 1.0
In-Reply-To: <rt-4.2.8-74611-1468271253-1135.41815-0-0@isc.org>
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Disposition: inline
X-RT-Interface: Web
References: <RT-Ticket-41815@isc.org> <56D0F465.5010402@illinois.edu>
 <rt-4.2.8-74611-1467922398-761.41815-5-0@isc.org>
 <57840A4F.1070709@illinois.edu>
 <rt-4.2.8-74611-1468271253-1135.41815-0-0@isc.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.2.8-74615-1468352092-1829.41815-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 511

On Mon Jul 11 21:07:33 2016, dmrz@illinois.edu wrote:
> Hi Thomas,
> 
> I like your parameter solution very much, and I confirm that the patch
> successfully prevents the problem scenarios I originally reported --
> thanks!
> 
> However, there's a variant scenario whose behavior still seems wrong:

Hi David,

Thank you for testing the patch.  We shall look into the scenario you
described soon but as we may take several days (or more) to get to
it I wanted to acknowledge your message sooner.

regards,
shawn