Graham Dumpleton commented on MODPYTHON-202:

mod_python should perhaps simply be using 'ap_accept_lock_mech' instead of 

The value of 'ap_accept_lock_mech' is more likely by default to be correct for 
what type of MPM is being used, if not, it can be overridden using the existing 
AcceptMutex directive, which if 'APR_LOCK_DEFAULT' is wrong for the MPM being 
used would have to be done to get the MPM to work anyway.

> Allow mechanism used by global mutex locks to be specified.
> -----------------------------------------------------------
>                 Key: MODPYTHON-202
>                 URL: https://issues.apache.org/jira/browse/MODPYTHON-202
>             Project: mod_python
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 3.2.10
>            Reporter: Graham Dumpleton
> When using experimental Apache ITK MPM, described at:
>   http://home.samfundet.no/~sesse/mpm-itk/
> global mutex locks will fail if Apache used semaphores because requests 
> against different virtual hosts run as different users and user will not have 
> permission to access the semaphore to lock it. See:
>   http://www.modpython.org/pipermail/mod_python/2006-November/022536.html
> for original mailing list post about this from Sam Morris.
> A suggested fix of finding a specific mechanism that works rather than 
> default used by Apache, seems to work:
>   http://www.modpython.org/pipermail/mod_python/2006-November/022537.html
>   http://www.modpython.org/pipermail/mod_python/2006-November/022538.html
>   http://www.modpython.org/pipermail/mod_python/2006-November/022539.html
> If available MPMs with such constraints are going to appear, may make sense 
> to have an option to configure which allows one to override at compile time 
> the default mechanism used for global mutex locks so that it can be made to 
> match what may be required for a specific MPM that Apache is compiled to use.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to