Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<3C31CACF.63C269DF@wapme-systems.de>
Date:	Tue, 01 Jan 2002 15:42:23 +0100
From:	Stipe Tolj <tolj AT wapme-systems DOT de>
Organization:	Wapme Systems AG
X-Mailer:	Mozilla 4.7 [de]C-CCK-MCD QXW0322b (WinNT; I)
X-Accept-Language:	de,en
MIME-Version:	1.0
To:	Sami Tikka <sami DOT tikka AT welho DOT com>
CC:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	Re: Apache/cygwin shutdown problem
References:	<3C2FB769 DOT 5030508 AT welho DOT com> <3C305864 DOT 312A66E6 AT wapme-systems DOT de> <3C30B86B DOT 9080602 AT welho DOT com>

Sami,

I CC'ed to cygwin@ instead, since Chris seems to dis-like the fact
that we keep this thread in cygwin-apps@.

Sami Tikka wrote:

> I've now discovered that my failure to shut down Apache has nothing to
> do with the cygwin version. I have produced two Apache configuration
> files. Start Apache with ok.conf and you can shut it down. Start Apache
> with failure.conf and the processes just hang on, never exiting and I
> have to use Task Manager to kill them.
> 
> To repro:
> 
> tar zxf apache_1.3.22.tar.gz
> cd apache_1.3.22
> ./configure --prefix=/test && make && make install
> # Copy ok.conf and failure.conf to /test/conf
> /test/bin/httpd -f /test/conf/ok.conf
> sleep 10
> kill -TERM $(cat ../logs/httpd.pid)
> # All Apache processes shut down
> /test/bin/httpd -f /test/conf/failure.conf
> sleep 10
> kill -TERM $(cat ../logs/httpd.pid)
> # Apache processes fail to exit
> 
> The only difference is that the failing configuration is set up to
> listen to both ports 80 and 8080.
> 
> I'm running an up-to-date Cygwin 1.3.6 on Windows 2000 Professional.
> 
> Is there anything that can be done to fix this? I'd really like to have
> the same Apache listen to both 80 and 8080 instead of running two Apaches.

Unfortunatly, I can confirm this now on my own setup :((

http://httpd.apache.org/info/known_bugs.html#listenbug

seems to give us more hints here, I'm investigating and comming back
if I get some solution.

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/

- Raw text -