is it safe to enable Lockfile for all mpms across all apache generations?

It looks like some poeple have a problem with LockFile directive being compiled to a hardcoded value. The problem: [Tue Nov 02 17:16:22 2004] [emerg] (13)Permission denied: Couldn't create accept lock Is it safe to set LockFile for all mpms? For apache 1.3? If yes, I'm going to add it to test f

Re: is it safe to enable Lockfile for all mpms across all apache generations?

On Wed, Nov 24, 2004 at 04:45:18PM -0500, Stas Bekman wrote: > It looks like some poeple have a problem with LockFile directive being > compiled to a hardcoded value. > > The problem: > > [Tue Nov 02 17:16:22 2004] [emerg] (13)Permission denied: Couldn't create > accept lock > > Is it safe to

Re: is it safe to enable Lockfile for all mpms across all apache generations?

Joe Orton wrote: On Wed, Nov 24, 2004 at 04:45:18PM -0500, Stas Bekman wrote: It looks like some poeple have a problem with LockFile directive being compiled to a hardcoded value. The problem: [Tue Nov 02 17:16:22 2004] [emerg] (13)Permission denied: Couldn't create accept lock Is it safe to se

Re: is it safe to enable Lockfile for all mpms across all apache generations?

Stas Bekman wrote: Joe Orton wrote: On Wed, Nov 24, 2004 at 04:45:18PM -0500, Stas Bekman wrote: It looks like some poeple have a problem with LockFile directive being compiled to a hardcoded value. The problem: [Tue Nov 02 17:16:22 2004] [emerg] (13)Permission denied: Couldn't create accept loc