On 29 June 2010 23:18, Bill Peck <[email protected]> wrote:
>
>
> On Mon, Jun 28, 2010 at 10:53 PM, Graham Dumpleton
> <[email protected]> wrote:
>>
>> On 28 June 2010 10:26, Bill Peck <[email protected]> wrote:
>> > We tried switching to worker method but then mod_krb5 crashed since its
>> > not
>> > thread safe.  So were stuck with pre-process method.
>>
>> Which is not an issue so long as you are using daemon mode and WSGI
>> applications are running in those daemon processes. That way you avoid
>> problems as described in:
>>
>>
>>  http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html
>>
>> which is just as relevant to mod_wsgi embedded mode if prefork used.
>>
>> Just because you use prefork doesn't mean you cant have thread
>> mod_wsgi daemon processes.
>>
>> Graham
>>
>
> No,  you had suggested we try the Woker MPM to see if that would solve the
> original problem of mod_wsgi *not* restarting the daemon processes.  In
> Pre-Fork MPM it will eventually stop spawning new procesess.

That post about mod_krb5 was the first post under that email name. I
thus assumed it was a side comment and not necessarily related to
problem being described by OP.

What is your relationship to ssteinerX because I am confused?

The comment still stands that prefork can be used with daemon mode
preferably used for WSGI application. The constraints on worker MPM
are obviously mod_php and now based on your comment also mod_krb5.

Separate to all that is the issue for daemon mode processes not being
restarted for some people with some specific Apache/APR/OS combination
when prefork used. At this point only a few people have reported this
and it is not across the board. Are you now stepping up and saying
that you are also getting the daemon process restart issue, or are you
actually ssteinerX?

Graham

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to