Akira Hayakawa

I see this issue too.

Sorry to start from my misunderstanding of the protocol. fuse 2.9.3 (protocol 7.19) has reply four methods for read but fuse 2.7.2 (protocol 7.8) has only two. So rust-fuse's implementation...

The easiest way to do this is making a daemon watching `service status` and when it's not running start it. the daemon should run outside the JVM akashic-storage daemon is...

``` 16702 20160401 14:51:56.805 [akashic-storage-akka.actor.default-dispatcher-10] DEBUG akashic.storage.service [Measure.scala:6] - -> GET Service 16703 20160401 14:51:56.806 [akashic-storage-akka.actor.default-dispatcher-10] DEBUG akashic.storage.service [GetCallerId.scala:16] - callerId: wg6fYjMPIiF5lQZ6Wa5ykrDgrB5qESr2WcKbGhZYBXjZjM7J0Csdhgin1H0WuWwU 16703 20160401 14:51:56.806 [akashic-storage-akka.actor.default-dispatcher-10] DEBUG akashic.storage.service [Measure.scala:10] -

According to the manual, ls alias is the valid command ``` EXAMPLES: 1. List buckets on Amazon S3 cloud storage. $ mc ls s3 ```

I removed the first line of "add buckets" test and it turned to green. The thing is amd64's mc can't list when there is no buckets.

I should reproduce this issue and feedback to upstream

I think there are potential users who want to use S3 protocol with distributed KV-store backends. It's fast and scalable. The interface of simple PUT/GET interfaces S3 nicely. Or, should...

If the KV-store's key is string and the value is byte array then it's very versatile.

I think this was because the daemon wasn't set up the max-content-length. it is by default MB so sending 160MB object will fault. But still strange it was killed by...