config/1510: LockFile not in httpd.conf; server fails if ServerRoot/logs deleted

[Mark Wilkinson <mh...@mft.co.uk>]

>Number:         1510
>Category:       config
>Synopsis:       LockFile not in httpd.conf; server fails if ServerRoot/logs deleted
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Thu Dec  4 03:40:01 PST 1997
>Last-Modified:
>Originator:     mhw@mft.co.uk
>Organization:
apache
>Release:        1.2.4
>Environment:
Solaris 2.5; problem applies to all environments
>Description:
I see a couple of mentions of problems which can be solved by including the
LockFile directive in httpd.conf. I've just run into the same problem myself
when I decided to move the server logs to /var/log and away from the config
files. I searched for "logs" in the configuration files and rewrote each
directive to give the full path to the new location I wanted. I then removed
the existing logs directory and found the server crashed when I told it to
reload the configuration. I presume this is because it couldn't create
accept.lock.
>How-To-Repeat:
Rewrite httpd.conf to point ErrorLog, TransferLog, PidFile and
ScoreBoardFile to a different directory. Delete the ServerRoot/logs directory.
Start the server.
>Fix:
I'd suggest including a prototypical LockFile entry in the distributed
httpd.conf file so that an administrator could change all lines containing
"logs" and have the resulting configuration work
>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. ]