[ https://issues.apache.org/jira/brow...action_12481939 ]

Sam Morris commented on MODPYTHON-202:
--------------------------------------

I did some investigating today and it seems that a pthread_mutexattr_setrobu
st_np function was introduced in glibc 2.4, so mod_python could check for it
 at build time.

My platform (Debian) will stick with glibc 3.2 until the release of Debian 4
.0 ("etch"), so I'm inclined to add a PythonOption for this 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 ag
ainst 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/...ber/022536.html
> for original mailing list post about this from Sam Morris.
> A suggested fix of finding a specific mechanism that works rather than def
ault used by Apache, seems to work:
>   http://www.modpython.org/pipermail/...ber/022537.html
>   http://www.modpython.org/pipermail/...ber/022538.html
>   http://www.modpython.org/pipermail/...ber/022539.html
> If available MPMs with such constraints are going to appear, may make sense to hav
e an option to configure which allows one to override at compile time the default me
chanism used for global mutex locks so that it can be made to match what may be requ
ire
d for a specific MPM that Apache is compiled to use.

[ Post a follow-up to this message ]