On Jun 16, 3:38 pm, Brian Neal <bgn...@gmail.com> wrote: > Well....instead of ranting about this here, why don't you open a > ticket and detail your findings. It is in the communities best > interest to have something like this fixed if it is indeed a problem. > Thanks.
Because the "fix" will introduce the original problem again - you need to clean up all socket or they might leak when you do a apache2ctl graceful, or when you have a high MaxClients count with mod_python (think large installations with worker mpm). So, what is less evil? Keep the connection alive, or kill it after every request? For us, keeping it alive works, but for others, it might break. You can't really file that as a bug, right? Reopened the original ticket, if it gets rejected, at least people can find the solution on google :P Miles --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
