From: Petter Reinholdtsen Date: Wed, 9 Apr 2014 09:32:31 +0000 (+0000) Subject: Typos. X-Git-Url: https://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/7bae9b8f5734d38d39cfbd402ef417e98827dada?ds=sidebyside Typos. --- diff --git a/blog/data/2014-04-09-nice-s3ql.txt b/blog/data/2014-04-09-nice-s3ql.txt index f7fbbaf131..dd987f1d65 100644 --- a/blog/data/2014-04-09-nice-s3ql.txt +++ b/blog/data/2014-04-09-nice-s3ql.txt @@ -36,7 +36,7 @@ package is included already. So to get started, run apt-get install s3ql. Next, pick a storage provider. I ended up picking Greenqloud, after reading their nice recipe on how -to use s3ql with their Amazon S3 service, because I trust the laws +to use S3QL with their Amazon S3 service, because I trust the laws in Iceland more than those in USA when it come to keeping my personal data safe and private, and thus would rather spend money on a company in Iceland. Another nice recipe is available from the article @@ -206,7 +206,7 @@ Backend reports that fs is still mounted elsewhere, aborting.

The file content is uploaded when the cache is full, while the metadata is uploaded once every 24 hour by default. To ensure the file system content is flushed to the cloud, one can either umount the -file system, or ask s3ql to flush the cache and metadata using +file system, or ask S3QL to flush the cache and metadata using s3qlctrl: