Per vhost socket dir and specified permission

[GoogleCodeExporter]

Hi.

As far as I can tell from the documentation, there is no way of controlling how 
the unix-sockets are created on an per vhost basis.

The issues with this for us is that we're running mpm-itk on our servers, so 
embedded mode is not really working for us in an performance perspective, as
mpm-itk shuts down the handler after each request. But at mpm-itk assigns
a user and group to the process, the application is not allowed to connect to
the domain socket (as it seems to have the wrong permission).

What I'd really like is a way to configure mod_wsgi to create sockets in a 
specified directory and permission on a vhost-basis.

Please correct me if I'm misinterperting the documentation - or if I'm just 
being stupid :-)

Original issue reported on code.google.com by kristian...@gmail.com on 18 Mar 2011 at 12:36

[GoogleCodeExporter]

What version of mod_wsgi are you using?

Support for ITK MPM is in mod_wsgi 3.3. You must however compile mod_wsgi from 
source code against Apache where the dev package (if using binary packages for 
Apache), are specifically for the ITK MPM. You cannot use a mod_wsgi.so binary 
compiled against a different MPM, nor compile against Apache header files for a 
different MPM.

Original comment by Graham.Dumpleton@gmail.com on 18 Mar 2011 at 4:11

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

I was using 2.8 which was the version in debian 5.0 - but 3.3 seems to be in 
Debian 6.0  - good stuff!

Thanks for your help.

You may close this as resolved :-)

Original comment by kle...@iterate.no on 22 Mar 2011 at 1:11

[GoogleCodeExporter]

For reference: seems this is broken in debian - filed a bug for it[0].

[0]: <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619252>

Original comment by kle...@iterate.no on 22 Mar 2011 at 2:48

[GoogleCodeExporter]

Original comment by Graham.Dumpleton@gmail.com on 29 Mar 2011 at 11:12

• Changed state: WontFix