Mailing-List:	contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT cygwin DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT cygwin DOT com>
List-Help:	<mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Message-ID:	<3CE3AE6D.4BF4EB63@wapme-systems.de>
Date:	Thu, 16 May 2002 15:04:45 +0200
From:	Stipe Tolj <tolj AT wapme-systems DOT de>
Organization:	Wapme Systems AG
X-Accept-Language:	de
MIME-Version:	1.0
To:	cygwin-apps <cygwin-apps AT cygwin DOT com>
Subject:	apache keep-alives keep hanging

Corinna and the others,

we'll need to have some kind of signal passing problem on Cygwin level
for Apache's child httpd processes.

As you may see from http://apache.dev.wapme.net/server-status the
childs don't seem to gracefully timeout when the parent process tells
them after timeout to do so.

I solved this by sending SIGKILL instead of SIGUSR2 in Apache's source
code. But I guess this is more a of a kludge then a solution.

Unfortunatly the interprocess signal passing problems appears at
high-load only. If someone of the core DLL guys and galls can check
this, please?!

I'll switch apache-1.3.24-5 to -6 and add the necessary code to use
SIGKILL instead of the usual signaling.

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

- Raw text -