Hi Brandon, A: Because it confuses the reader. Q: Why? A: No. Q: Should I write my response above the quoted reply?
..so please quote properly, as I'm doing in the rest of this mail: On Jun 21 2016, Brandon Orwell <[email protected]> wrote: > Just so everyone knows, since disabling SSL via backend option "no-ssl" on > Amazon S3, I haven't had a single incidence of the transport endpoint not > connected error killing my mount. I have had three simultaneous s3 buckets > mounted and transferred well over 8TB now without the endpoint > disconnecting. I got the idea after seeing an SSL error in the mount.log > after the last error and decided to disable it. I take that to mean you didn't read my answer to your report? In http://article.gmane.org/gmane.comp.file-systems.s3ql/1469 I actually told you about this very workaround. > It has been fine since. I > don't know if this is a coincidence or if there's an issue with SSL, No, that's not a coincidence. The problem is with Python's OpenSSL integration, so disabling SSL ensures that this problem will not happen. Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- 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.
