Hi Adam, I think you may want to set the CP cfonfig: autoreload.on : False and powercycle the system. The auto-restart may be causing the "already-in-use" socket err.
Also, pl. note the "Caveats" section of Johnathan's article. This method you've chosen will very likely _not_ work if you are using CP's in-memory session filters. Behavior was utterly unpredictable for me. Best, /venkat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
