delorie.com/archives/browse.cgi | search |
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: | <3BD2BAF2.43E33BE9@wapme-systems.de> |
Date: | Sun, 21 Oct 2001 14:09:22 +0200 |
From: | Stipe Tolj <tolj AT wapme-systems DOT de> |
Organization: | Wapme Systems AG |
X-Mailer: | Mozilla 4.51 [de] (WinNT; I) |
X-Accept-Language: | de |
MIME-Version: | 1.0 |
To: | Alvin Ng <rebooting AT hotmail DOT com> |
CC: | cygwin AT cygwin DOT com |
Subject: | Re: Apache/PHP Problem:CLOSE_WAIT sockets |
References: | <LAW2-F61XLuSbh29cM30000d0d0 AT hotmail DOT com> |
> I'm using the Apache + PHP setup on Cygwin, which was self compiled. The > plain HTML stuff that apache serves out seem to be ok, but anything > involving PHP talking to PGSQL via TCP will run properly, but the port that > served the PHP page will have a CLOSE_WAIT state after that. After a while > of continuous operation the CLOSE_WAIT state ports stacks up. > > Shutting down the Apache server also generates this in the logs: > > ---------- > $ tail -f /usr/local/apache/logs/error_log > [Sat Oct 20 22:14:51 2001] [warn] child process 1000 still did not exit, > sending > a SIGTERM > [Sat Oct 20 22:14:51 2001] [warn] child process 1136 still did not exit, > sending > a SIGTERM > > [snip]---- that unfortunatly ok for the cygwin platform. We have problems with apache for cygwin and signals. This has been reported to the cygwin core developers, unfortunatly there has not been any volonteer to track the problem in the cygwin lib itself. First of all, which cygwin version are you running? Does that meen the php script runs forever and does not output anything? How did you see about CLOSE_WAIT states in sockets? Stipe tolj AT wapme-systems DOT de ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |