![]() Note that Jottacloud requires the MD5 hash before upload so if the source does not have an MD5 checksum then the file will be cached temporarily on disk (wherever the TMPDIR environment variable points to) before it is uploaded. Jottacloud supports MD5 type hashes, so you can use the -checksum flag. In my case, my SD card has little space and I have multiple external drives and therefore want to set $TMPDIR to a specific folder on separate drives when I copy. If you ask me, this should be mentioned just below configuration with an example on how to solve this. The first account plan is 29 USD per month, which goes for 1000 subscribers to your service. The ConvertKit pricing follows three plans that are dependent on the number of total subscribers you want to provide services. So, I highly recommend adding a bigger NOTE at so people that use crypt and have limited storage space for the /tmp folder can easily spot this issue. Other cheap email tools available online do not offer the same type of features this cheap for smaller plans. In addition to that, I tried to change the tmp-dir with -cache-tmp-upload-path. Especially frustrating was the part that I thought not using -c should solve this, as well as using -ignore-checksum. ![]() I had an unfortunate start with rclone and Jottacloud as this issue has bothered me for many hours without figuring out why I was seeing TIMESTAMP ERROR : FILE: Failed to copy: failed to calculate MD5: write /tmp/rclone-*md5-*: no space left on device. Providing a cut down interface Rewind (say) would be much easier - maybe that is the way to go. The encryptor with seek would be equally challenging. Crypt has a file decryptor with Seek capability and that was extremely challenging to get correct. If the io.Seeker wasn't available it would do what it does at the moment. Then the jottacloud backend would be able to do a type assertion for io.Seeker and if found it could read the file to make the MD5, seek, then read it again. all the accounting gubbins for uploads implements io.Seeker.local upload streams implement io.Seeker.crypt upload streams implement io.Seeker.The only way this could possibly work is if One thing to bear in mind is that encrypting the same file twice won't get the same result (becuase of the nonce at the start of the file) so this needs to be done in the same encryption stream. ![]() Rclone uses a streamed architecture for transferring files so the backends don't get files to upload, they get file streams (an io.Reader in go speak). Alas this is a lot harder than it appears!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |