quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Graham Dumpleton (JIRA)" <j...@apache.org>
Subject [jira] Created: (MODPYTHON-202) Allow mechanism used by global mutex locks to be specified.
Date Wed, 08 Nov 2006 22:42:51 GMT
Allow mechanism used by global mutex locks to be specified.

                 Key: MODPYTHON-202
                 URL: http://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:


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:


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:


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.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message