public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Alvin Ng" <rebooting@hotmail.com>
To: cygwin@cygwin.com
Subject: Apache/PHP Problem:CLOSE_WAIT sockets
Date: Sat, 20 Oct 2001 07:40:00 -0000	[thread overview]
Message-ID: <LAW2-F61XLuSbh29cM30000d0d0@hotmail.com> (raw)

Hi,

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

Apache 1.3.22
PHP 4.0.6
Postgres(default Cygwin install)

Does anyone have the same problem running a setup like this under Cygwin? Or 
should I stick to the windows installers? Please advise.

-Alvin

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

             reply	other threads:[~2001-10-20  7:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-20  7:40 Alvin Ng [this message]
2001-10-21  5:11 ` Stipe Tolj
2001-10-22  8:33 Alvin Ng
2001-10-24  0:14 ` Stipe Tolj
2001-10-24  7:54   ` Christopher Faylor
2001-10-24  9:55     ` Stipe Tolj
2001-10-24 10:24       ` Christopher Faylor
2001-10-24 23:52         ` Stipe Tolj
2001-10-24  8:33 Alvin Ng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=LAW2-F61XLuSbh29cM30000d0d0@hotmail.com \
    --to=rebooting@hotmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).