Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 72722 invoked by uid 500); 24 Oct 2000 11:36:23 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 72696 invoked from network); 24 Oct 2000 11:36:21 -0000 Date: Tue, 24 Oct 2000 12:36:01 +0100 From: Manoj Kasichainula To: new-httpd@apache.org Subject: Re: Suexec Message-ID: <20001024123601.A2894@manojk.users.mindspring.com> Mail-Followup-To: new-httpd@apache.org References: <200010232025.e9NKPE225167@www.jetnet.co.uk> <20001024122754.A1036@manojk.users.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.10i In-Reply-To: <20001024122754.A1036@manojk.users.mindspring.com>; from manoj@io.com on Tue, Oct 24, 2000 at 12:27:54PM +0100 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Tue, Oct 24, 2000 at 01:38:15AM -0700, rbb@covalent.net wrote: > > We should definately NOT have suexec enabaled by default unless we know > for sure that the platform can support it. Once I can dive back into the configure structure and figure out how to enable mod_suexec for Unix only, I will fix this. (for anyone else who wants to try, the enabling of mod_suexec is in src/modules/standard/config.m4)