www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jay <...@cruzio.com>
Subject os-bsdi/835: accept.lock not created in correct log directory
Date Tue, 08 Jul 1997 01:40:07 GMT

>Number:         835
>Category:       os-bsdi
>Synopsis:       accept.lock not created in correct log directory
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache (Apache HTTP Project)
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Mon Jul  7 18:40:01 1997
>Originator:     jay@cruzio.com
>Organization:
apache
>Release:        1.2.1
>Environment:
BSDI 3.0 using gcc and apache 1.2.1
>Description:
My BSDI 3.0 comes with apache 1.1.3 which is configured to
place all log files in /var/log/httpd, per the ErrorLog and
TransferLog directive.  But there is not "logs" directory in
the apache install directory.

Apache 1.2.1 needs a "logs" directory at the same level as the
conf and docs directory.  This is an undocumented change in
requirements?

Previous versions of apache did not require the "logs" directory.


A quick grep of httpd.h reveals the problem:

httpd.h:#define DEFAULT_LOCKFILE "logs/accept.lock"
>How-To-Repeat:
Use ErrorLog and TransferLog directives to point to /tmp.
Remove the "logs" directory in the apache install directory.
Now start httpd.  I get a complaint about unable to create a
file.  
>Fix:
Make it clear that the "logs" directory must exist even if
you redirect your ErrorLog and TransferLog somewhere else
>Audit-Trail:
>Unformatted:



Mime
View raw message