Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3DE4CC34.986459AC@wapme-systems.de> Date: Wed, 27 Nov 2002 14:44:20 +0100 From: Stipe Tolj Organization: Wapme Systems AG X-Accept-Language: de MIME-Version: 1.0 To: Paul Nolan , "cygwin AT cygwin DOT com" Subject: Re: apache 1.3.27 on cygwin 1.3.16-1 References: <3DE3410C DOT 4090409 AT atrove DOT com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Paul, Paul Nolan schrieb: > > Hi, > I found your web site while looking for a reason why > apache doesn't work properly on the latest cygwin version, > actually I don't think it worked properly on cygwin 1.3.12 either. it works, but not stable as my experiences have shown. I got http://apache.dev.wapme.net now running with apache-1.3.27 since some time and that working as expected, it's cygwin-1.3.10-2 underneith. There is something wrong in the cygwin-1.3.12 (and up) versions concerning Apache. > Basically it doesn't load share properly across all running > processes. If you look at the server-status page. Only one process is > ever listed. Can you snapshot the html output and mail it to me. > I found your server-status page at > http://apache.dev.wapme.net/server-status > it looks fine. > What version of cygwin are you running??? It runns "old" 1.3.10-2. Which is currently the only one working reliable and stable for me. I'd like to hear from the Cygwin core guys what connection or socket internal things have changed since then. > I've noticed if you set MaxRequestsPerChild to 50 to see what happens > when the process it suppose to be refreshed, it stops and the page can't > be loaded. > NOTE: Turn KeepAlive Off as well so that each page load counts as a request. > > i.e. Change the following in the default cygwin apache httpd.conf that > comes with the cygwin release. Current that apache is 1.3.24 (the > behavior is still there in the current release of apache 1.3.27 as well) yep, it's not inside Apache, I suppose the problem is resulting from some change in Cygwin itself since 1.3.10-2. I had any apache version running successfully on cygwin-1.3.10-2. > KeepAlive Off > MaxRequestsPerChild 50 > > After 50 page loads of server-status apache will lock-up. > > Have you seen this behavior? yes, unfortunatly. If you are interested in getting this fixed ASAP, please enfore the cygwin developers to have a deeper look into this. My time is currently very limited. Stipe tolj AT wapme-systems DOT de ------------------------------------------------------------------- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: info AT wapme-systems DOT de Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are -- 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/