config/1422: no configuration directive for lockfile in configuration

[Roy-Magne Mo <rm...@www.hivolda.no>]

>Number:         1422
>Category:       config
>Synopsis:       no configuration directive for lockfile in configuration
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Nov 15 12:40:01 PST 1997
>Last-Modified:
>Originator:     rmo@www.hivolda.no
>Organization:
apache
>Release:        1.3b2
>Environment:
uname -a: Linux tux 2.0.25 #3 Fri Oct 17 15:30:41 GMT 1997 i686
>Description:
[Sat Nov 15 22:09:34 1997] [emerg] (2)No such file or directory: Cannot open lock file: /etc/httpd/apache/logs/accept.lock.14241

There is no configuration directive for where apache should but it's lock-files in 1.3b2. 

Since this error AFAIK wasn't posted as a bug, I thought you should make a note of it. 

Best regards - thank's for you wonderful job.
>How-To-Repeat:
Starting httpd with 'httpd -d /some/directory'  
where /some/directory/logs isn't the directory 
where you want to put your lock-files
>Fix:
Mine fix were to link in the logs to the documentroot. But i would prefer having
these files in /var/lock. 

I believe a directive in httpd.conf and possibly support for the directive in the source would suffice
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]