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
Date: Mon, 4 Jun 2001 08:11:45 +0200 (MEST)
To: Stipe Tolj <tolj AT wapme-systems DOT de>
Cc: cygwin AT cygwin DOT com
Cc: cygwin AT cygwin DOT com
Subject: Re: Apache 1.3.20 & apxs
References: <3B1767AE DOT 6E649D2E AT wapme-systems DOT de>
Message-ID: <25200.991635105@www12.gmx.net>
From: "S. L." <s_i_lao AT gmx DOT net>
MIME-Version: 1.0
X-Authenticated-Sender: #0006551723 AT gmx DOT net
X-Mailer: WWW-Mail 1.5 (Global Message Exchange)
X-Authenticated-IP: [217.156.64.138]
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

[...]
> >    b. (and here is an yumyumyum :) php4 does load, and it's working
> > properly.
> 
> can you post me some kind of logs or patches you did to make the modules
> into
> single DLLs and what happened, I will try to pass things to apache.org as
> far as
> they are stable.


After failures with mod_cgi and mod_log_config, I've noticed that those 2
modules wouldn't link with libhttpd.a. The lib they wanted was libhttpd.dll. So
I made the build with:

./configure --enable-module=so --enable-rule=SHARED_CORE --enable-rule=EAPI
--enable-shared=max --enable-shared=proxy --with-perl=/usr/local/bin/perl
make
make -i
make -i install

and the modules with:

for f in *.lo; do /usr/local/apache/bin/apxs -c -o `basename $f .lo`.dll $f
../../libhttpd.dll; done

> 
> > Stipe has done a very good work. I would suggest to include in the patch
> for
> > apache 1.3.x tree, the addition of __CYGWIN__ to "#ifundef TPF"
> directive at
> > 2287 line in http_protocol.c, as posted in a previous message; this
> solves
> > the w9x cgi execution, which, without it, ends the connection only after
> > server timeout. This modification could have some connotation only for
> NT/2k,
> > where the server works properly in either case.
> 
> I'll check that impact.
> 
> I have noticed that a build with mod_ssl+mod_php consumes memory (leaks)
> and the
> httpd childs seem not to die properly. But it doesn't seem to happen
> running ony
> the core apache modules.
> 
> This is to be investigated too.
> 

Actually I've not used in production the last versions of Apache & co. and
cygwin. On my NT I have a "SERVER_SOFTWARE = Apache/1.3.12 (Cygwin) PHP/4.0.2
mod_ssl/2.6.6 OpenSSL/0.9.5a", with your 1.3.9 patch applied (ssl'n'php
included in libhttpd.dll). I didn't find any performance problem, although having
a poor hardware PDC configuration, with cygwin sshd and apache not running as
services, but launched from a tk console so they can work in background
without any problems, after finishing tk.

But on my w9x there's no other mean to pass over the keeping connection
alive until the time out expires, after running a cgi script (not a php). The
problem stands while static linking the httpd, too.

Regards,

                       SLao

-- 
Sent through GMX FreeMail - http://www.gmx.net

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple