Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <00f801c14cb5$a91ebcc0$01000001@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Stipe Tolj" <tolj AT wapme-systems DOT de>
Cc: <cygwin AT cygwin DOT com>
References: <3BBB6E37 DOT DD0CD8BF AT wapme-systems DOT de> <039001c14c57$9548da90$01000001 AT lifelesswks> <3BBC171E DOT 884AB8CF AT wapme-systems DOT de> <00d101c14cab$929c9b20$01000001 AT lifelesswks> <3BBC261C DOT EA8ECAE3 AT wapme-systems DOT de>
Subject: Re: apache-1.3.x strange behaviour on keep-alives
Date: Thu, 4 Oct 2001 19:19:18 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

----- Original Message -----
From: "Stipe Tolj" <tolj AT wapme-systems DOT de>
To: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
Cc: <cygwin AT cygwin DOT com>
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/