Received: (qmail 6855 invoked by uid 2012); 30 Oct 1998 16:42:11 -0000
Message-Id: <19981030164211.6854.qmail@hyperreal.org>
Date: 30 Oct 1998 16:42:11 -0000
From: Niall Doherty <ndoherty@eei.ericsson.se>
Reply-To: ndoherty@eei.ericsson.se
To: apbugs@hyperreal.org
Subject: DOC_ROOT and LOG_EXEC are set in Makefile and override suexec.h
X-Send-Pr-Version: 3.2

>Number:         3316
>Category:       suexec
>Synopsis:       DOC_ROOT and LOG_EXEC are set in Makefile and override suexec.h
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Oct 30 08:50:01 PST 1998
>Last-Modified:  Sun Nov  8 13:28:17 PST 1998
>Originator:     ndoherty@eei.ericsson.se
>Organization:
>Release:        1.3.3
>Environment:
SunOS 5.5.1 Generic_103640-08 sun4u sparc SUNW,Ultra-1
>Description:
DOC_ROOT and LOG_EXEC are both set in the Makefile that is
generated after a configure. However, neither of these variables
can be set with an option to configure.

The suexec.h file options are therefore overridden and the
following lines are therefore ignored:

#ifndef DOC_ROOT
#define DOC_ROOT "/www"       /* Need me? */
#endif

(the same for LOG_EXEC)

A template is kept (on our site) for suexec.h which is copied
into the src/support directory before compilation (after a diff
with the new version of course :-) and we initially had a problem
figuring out what was wrong.
>How-To-Repeat:
-
>Fix:
Add the following options to configure:

  --suexec-docroot
  --suexec-logexec
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: lars
State-Changed-When: Sun Nov  8 13:28:17 PST 1998
State-Changed-Why:

Two new options (--suexec-docroot and --suexec-logfile)
have been added to APACI to allow full control of      
the suEXEC setup.                                   

Release-Changed-From-To: 1.3.2 and 1.3.3-1.3.3
Release-Changed-By: lars
Release-Changed-When: Sun Nov  8 13:28:17 PST 1998
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]