>For Apache 2.0 and 2.2, either the single threaded 'prefork' or multithreaded 'worker' Apache MPMs can be used.
>To be able to make use of daemon mode of mod_wsgi, either Apache 2.0 or 2.2 is required and the corresponding Apache runtime (APR) libraries must have been compiled with support for threading.
Actually there is nothing about that is not possible to use worker MPM
and daemon mode.
So, I'm using it and have no problem at all.
...
ServerName vspolny.ru
WSGIDaemonProcess vspolny user=www group=www
httpd -V
Server version: Apache/2.2.15 (FreeBSD)
Server built: Jun 12 2010 21:08:00
Server's Module Magic Number: 20051115:24
Server loaded: APR 1.4.2, APR-Util 1.3.9
Compiled using: APR 1.3.9, APR-Util 1.3.9
Architecture: 32-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
On Oct 29, 7:22 pm, "bax...@gretschpages.com" <mail.bax...@gmail.com>
wrote:
> I'm finding conflicting info regarding preferred server
> configurations.
>
> I'm using Nginx for static, passing off to Apache/mod_wsgi for django
> stuff. Currently, wsgi is in daemon, and I'm using the worker MPM.
> From some sources I've seen that is ideal, but I notice in the django
> docs that prefork MPM is better. But then I read you can't use prefork
> if wsgi is in daemon mode.
>
> So I'm confused, and hoping someone can clarify for me.
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment