Bug 50521 - Comment at top of sample main config file is wrong
Summary: Comment at top of sample main config file is wrong
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: Build (show other bugs)
Version: 2.2.16
Hardware: PC Linux
: P2 normal with 1 vote (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-12-25 08:48 UTC by Charles
Modified: 2018-11-07 21:08 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles 2010-12-25 08:48:07 UTC
The comment at the top of the sample main config file is generated (this sample from Slackware64 13.1) as:

# ...  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/httpd/foo_log"
# with ServerRoot set to "/usr" will be interpreted by the
# server as "/usr//var/log/httpd/foo_log".

The leading / of both /var strings should not be present.

A possible patch (for 2.1.7, created by "ponce" not me and online at http://ponce.cc/slackware/testing/other/patches/rel_logfiledir.patch) is

--- httpd-2.2.17/configure.orig	2010-12-25 11:46:47.000000000 +0100
+++ httpd-2.2.17/configure	2010-12-25 11:53:58.000000000 +0100
@@ -3185,7 +3185,8 @@
     # it wasn't so return the original
     rel_logfiledir="$exp_logfiledir"
 fi
-
+# I said strip it
+rel_logfiledir="`echo ${rel_logfiledir} | sed -e 's#^/##'`"
 
   APACHE_VAR_SUBST="$APACHE_VAR_SUBST rel_logfiledir"
Comment 1 ponce 2010-12-25 12:46:22 UTC
maybe this is more appriopriate?

http://ponce.cc/slackware/testing/other/patches/strip_leading_slash_from_rel_logfiledir.patch

the problem seems to be in the variable keeping a leading path inheriting it from exp_logfiledir.
Comment 2 William A. Rowe Jr. 2018-11-07 21:08:15 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.