> That makes me suspicious. S3QL 1.11 does not use python-dugong, so you > must have encountered a different error.
By 'issue', I only meant that I was having problems with reliability under 1.11 and upgraded in the hope of solving this. > Could you please post the relevant contents of mount.s3ql when you > encounter the problems, for both S3QL 2.8.1 and S3QL 1.11? Please make > sure that you include the full traceback. Of course; I'll do that this evening. The author of the article that I linked to reports that "My connections have been stable so far, with one strange exception." which suggests that it's something about the setup at my end. I'll also try using a server I have access to elsewhere. Regards, Adam -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
