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
X-Originating-IP: [202.156.2.243]
From: "Alvin Ng" <rebooting AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Apache/PHP Problem:CLOSE_WAIT sockets
Date: Wed, 24 Oct 2001 15:33:33 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <LAW2-F94HvAo1jvDWsJ0001249a@hotmail.com>
X-OriginalArrivalTime: 24 Oct 2001 15:33:33.0421 (UTC) FILETIME=[3D7D81D0:01C15CA1]

I'll see if I have the time to build a debugging version of Apache. I'm kind 
of doing this 4-8 hours a week so I may not have the resource to do so.

I'm not even sure where the error is coming from(PHP or Apache or Postgres).

I took the easy way out I guess :)

-Alvin


>I don't know how many people are willing to download apache, set it up, and 
>run it, to duplicate your problems.
>
>So, you're welcome to keep asking for "the Cygwin Core team" to debug this 
>but I suspect that you'll have a long wait unless you can dilute the 
>problem into a simple test case.
>
>Or, if you have a failing condition, you might want to attach the debugger 
>to it and poke around to see what is going on. You will need to build a 
>debugging version of cygwin to get any useful info of course.
>
>cgf
>
>--


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp


--
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/