Peter Schüller <schuelle...@gmail.com> writes: > Is there a way to mount s3ql read-only by setting bucket permissions in a > way that > * mounting is still possible, but > * changing the file system is not possible? > > If I disable all Put/Delete actions of S3 then mounting fails, probably > because the fact that the FS is mounted is stored in some special file in > the bucket. I can understand this, but what happens if I allow writing just > to that file and not to the rest of the bucket? Is it even "one file"?
Well, it's just one file, but a different on every mount. On every mount, S3QL creates a file s3ql_seq_no_XX, where XX is an increasing number, and deletes the n-th most recent s3ql_seq_no_YY file. If you can configure AWS to allow that, then it should work. > To clarify: I do not want to mount in multiple locations, I just want to > have a user that has no possibility to destroy the data but can still read > it. That user will likely get warnings and/or crashes because of apparent file system corruption if he tries to access data that has been modified by the other active mount. 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 s3ql+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.