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>
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3C45CF73.7B050051@wapme-systems.de>
Date: Wed, 16 Jan 2002 20:07:31 +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: cygwin-apps AT cygwin DOT com
Subject: Re: Apache 1.3.22-3 ready to go?!
References: <3C43EF02 DOT 239CC44A AT wapme-systems DOT de> <20020115120344 DOT T2015 AT cygbert DOT vinschen DOT de> <3C440FC8 DOT BDBCB655 AT wapme-systems DOT de> <20020115122535 DOT V2015 AT cygbert DOT vinschen DOT de> <20020115133314 DOT Y2015 AT cygbert DOT vinschen DOT de> <3C45382F DOT 921ADB4B AT wapme-systems DOT de> <20 <20020116181920 DOT R2015 AT cygbert DOT vinschen DOT de>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Corinna Vinschen wrote:
> 
> Yup.  It's using the wrong path.  And it doesn't work that
> way apparently without the option not to fork.
> 
> I grubbed a bit in the apache documentation and found that the
> native Windows version has two command line options `-n' and
> `-k' to install, stop and restart apache as service.
> 
> Wouldn't it make sense to use that part of the source code for
> the Cygwin apache, too?  It must be similar to the service stuff
> in inetd.
> 
> Anyway, I have no preferences.  You can use your own option for
> starting with cygrunsrv or the native Windows options, whatever
> is less work.

I'll see how dificult the native Win32 thing is to include, otherwise
I'll drop back to sshd's option to "not fork" for cygrunsrv support.

> Another question:  Are you planning to support mod_ssl in future
> as well?  I'm sure it would be most appriciated.  If I'm not
> completely off track, it's needed to allow https connections to
> apache, right?

yep, mod_ssl is the glue between Apache and OpenSSL to implement the
HTTPS scheme. BTW, mod_ssl is "more then a regular" Apache API
modules, because Ralf adds the EAPI (enhanced API) to the Apache
source tree. It's required to get additional hooks into Apache's core
structure, which are not supported by the regular API.

mod_ssl is supposed to compile and build OOTB on Cygwin. See CAMP
distribution page at http://apache.dev.wapme.net/packages/ for a
working version under Cygwin.

I'm not quite sure how we may include Apache shared module DLL
packages to the Cygwin net distro?! I would like to keep the core
distribution stand alone and add something like "mod_ssl-2.x.tar.bz"
for the shared modules only. I guess this may be a usefull way?!

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