On Sun, Mar 29, 2009 at 12:35, Graham Dumpleton <[email protected]>wrote:
> Don't know if that was related to zombie issue you asked about on > mod_wsgi list back in November or not. You were asked to supply some > more specific information but you never responded. Bit hard to solve > what ever problem it was when you don't followup about it. -( > You're absolutely right of course. I should have troubleshooted it better. I am 99% sure it's not mod_wsgi fault. After all, even now it leaks memory like there is no tomorrow so monit have to restart it about once in 4-6 days. The thing is, I am not such a great programmer, I don't have tons of admin expertise (nor I am too keen to get it) and there are pressing concerns (as always) such as site being not available to users. I was looking for the easiest/fastest route possible and nginx/http proxy worked for me. PS: as for automatic code reloading, we did used it, on production too. May be we shouldn't be. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
