httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Terbush <>
Subject Re: Followup re Apache 1.2.4 - hardwired accept lock ... message (fwd)
Date Sun, 31 Aug 1997 16:05:56 GMT

This came up recently when I asked the following question but
received no response. 

When Jim, Marc, Dean and I put our heads together on this lockfile 
issue, I had provided some code that located the default lockfile 
location to the same place as the PidFile. That seems to be the 
best way to deal with this IMO. Was there something wrong with that 

> Take II
> ---------- Forwarded message ----------
> Date: Sun, 31 Aug 1997 12:55:59 +0100 (BST)
> From: WWW server manager <>
> To:
> Subject: Followup re Apache 1.2.4 - hardwired accept lock ... message
> I've now discovered that although a quick examination of the source suggested
> there was no way to override the location of the accept lock, it is in fact 
> settable by the LockFile directive.
> However, I do not feel it is my fault that I overlooked the existence of this 
> directive, or the need to use it:
>  * there is no mention of it in the sample configuration files or the 
>     HTML "New features in Apache 1.2" document.
>  * it is mentioned in the src/CHANGES files, but with no hints of its
>    importance or when it might be needed
>  * it is mentioned in the main Apache documentation (amidst dozens of other
>    directives, of course) but in terms implying its main use is with NFS 
>    mounted directives (not relevant here). 
> Given the minimal coverage in documentation and absence from the sample 
> configuration files, overlooking it and spending time hunting around for an 
> explanation of the newly-encountered problem seems more likely than 
> anticipating the need and adding it to the configuration files. Of course,
> it will not affect people using the sample directory layout, but for anyone
> who choose a different location for the logs (especially where they've been
> using a different layout for a long time, without such problems) it's liable to 
> cause trouble.
> For the benefit of people yet to trip over this, please improve the
> documentation and sample config files to make clear the existence and
> significance of the LockFile directive.
>                                 John Line
> -- 
> University of Cambridge WWW manager account (usually John Line)
> Send general WWW-related enquiries to

View raw message