Bug 61899

Summary: Documentation error in Apache/2.0.48 port: default httpd.conf
Product: Ports & Packages Reporter: Marloes de Boer <marloes-fbsd>
Component: Individual Port(s)Assignee: Clement Laforet <clement>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Marloes de Boer 2004-01-25 18:10:09 UTC 
	In the Apache/2.0.48 port, with recent CVSup, an error appears in the default httpd.conf. I noticed an inconsistency in the section that starts at line 24:

# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path.  If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "/var/log/foo.log"
# with ServerRoot set to "/usr/local" will be interpreted by the
# server as "/usr/local//var/log/foo.log".

Obviously, the example states behaviour that is entirely contradictory to what is said above it. Assuming this was an error Apache itself i searched their CVS for this particular file, and found the following: 

http://cvs.apache.org/viewcvs.cgi/*checkout*/httpd-2.0/docs/conf/httpd-std.conf.in?content-type=text%2Fplain&rev=1.56

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

Thus the replacement must have gone wrong. I'm not sure whether this is an error in the Apache-code or in the way portinstalls work.

How-To-Repeat: 	install the apache2 port
Comment 1 Pav Lucistnik freebsd_committer freebsd_triage 2004-01-25 18:15:36 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->clement

Over to maintainer.
Comment 2 Clement Laforet freebsd_committer freebsd_triage 2004-02-11 12:06:19 UTC 
State Changed
From-To: open->closed

Since we put by default logs in /var/log/httpd*, the default 
config file looks wrong. So it's an apache problem, not a port 
one.