> > does anyone knows why it is so ? > > to circumvent the problem I set mysql wait time out to 120 s instead > > of 28800 by default > > This doesn't appear to work for us. I believe it is because changing > the global wait_timeout (in my.cnf) (for some reason) only affects > tcp connections and not interactive connections or socket connections > ( DISCLAIMER: I read this on experts exchange ). there is another server variable for interactive connections time out (I don't remember the name it is in mysql admin browser next to wait_timeout) it is also 28800 s by default the thread says it was broken in rev 5482 and so nobody uses 5482+ ? regards, pascal --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
