Subject: Re: apache-1.3.x strange behaviour on keep-alives
From: "Robert Collins" <[email-masked]>
To: "Stipe Tolj" <[email-masked]>
Cc: <[email-masked]>
Date: Thu, 4 Oct 2001 19:19:18 +1000

----- Original Message -----
From: "Stipe Tolj" <[email-masked]>
To: "Robert Collins" <[email-masked]>
Cc: <[email-masked]>
Sent: Thursday, October 04, 2001 7:04 PM
Subject: Re: apache-1.3.x strange behaviour on keep-alives

> > The first thing _someone_ has to do is identify _when_ the bad
behaviour
> > was introduced. Then it's realistic to scream "<cvs committers
name>"
> > Why, Oh Why, did you do this to apache and squid!!. Until then,
there is
> > no point.
> >
> > If you want this solved, build a .dll from 1/2 way between, and then
> > install it. If it doesn't show the symptom, go forward 1/4 the time.
> >
> > I'm willing to bet that only four iterations will be needed to
isolate a
> > single ChangeLog entry that affects sockets/tcp. At that point,even
if
> > there are more changes in the time period, it's pretty certain which
one
> > will be the culprit.
>
> ok, I'll start to check if 1.1.8-2 is working ok (which was a very
> stable release) and then iterate as described.
>
> Thanks Robert.
>

No problems :}. When you start iterating, bear in mind, that to the best
of my knowledge 1.3.2 was stable with respect to this bug.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/