You are viewing a plain text version of this content. The canonical link for it is here.
Posted to test-dev@httpd.apache.org by Stas Bekman <st...@stason.org> on 2004/11/24 22:45:18 UTC

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 framework globally.

Thank you!

p.s. the problem reported and the diagnose made in this thread:
http://thread.gmane.org/gmane.comp.apache.mod-perl/15547


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

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

Posted by Stas Bekman <st...@stason.org>.
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 lock
>>>
>>> Is it safe to set LockFile for all mpms?
>>
>>
>> Yes, looks like it should be.
>>
>>> For apache 1.3?
>>
>>
>> I think so too.
> 
> 
> Excellent, thanks Joe!

Unfortunately it's not the case. winnt croaks on this directive.

http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile
Module:	leader, perchild, prefork, threadpool, worker

so I adjusted it to be enabled for those mpms that support it.

-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

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

Posted by Stas Bekman <st...@stason.org>.
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 set LockFile for all mpms?
> 
> Yes, looks like it should be.
> 
>>For apache 1.3?
> 
> I think so too.

Excellent, thanks Joe!


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

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

Posted by Joe Orton <jo...@redhat.com>.
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 set LockFile for all mpms?

Yes, looks like it should be.

> For apache 1.3?

I think so too.

joe