On Friday, April 18, 2014 12:15:44 PM UTC-5, Nikolaus Rath wrote: > > Randy Black <[email protected] <javascript:>> writes: > > when specifying an auth file, why does the mounting process continue to > > prompt for credentials? > > > > mount.s3ql --cachedir /root/.s3ql-cache --authfile /root/s3ql_auth > > --allow-root swiftks://<host>:<port>/<region>/<container> /s3ql > > > Probably because the storage URL in your auth file is subtly different > from the storage url that you pass to mkfs. > > Please copy & paste (don't retype) both your command line and the > contents of you authinfo file without manually editing the storage url > (but don't forget to remove the passwords). If you're obfuscating the > URL, it's near impossible to help (for example, is there really a space > after <container> and before /s3ql? >
B-I-N-G-O auth file storage url had a forward slash where it should have had a colon. This was between the region and container. Thanks Nikolaus > 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.
