Hello Arelor!

** On Monday 25.09.23 - 18:21, Arelor wrote to August Abolins:

 >> ..but, the contents of sss did NOT end up in /arn/archive.
 >> Instead, the encrpyted dir/files were deposited in the root
 >> of my account.  

 A> That is because your crypt remote is configured to use
 A> test1: instead of test1:/arn/archive as its target.

OK.. so it appears that it created the encrypted directories  
because I configured it to do that.  Had I stipulated that  
mycrypt: NOT encrypt the directories, using mycrypt:/arn/ 
archive would have placed the encrypted files in the actual  
/arn/archive location?


 A> Think of "mycrypt:" as a virtual folder that resides in
 A> wherever you point it at. If you instruct rclone to put
 A> stuff in mycrypt:/arn/archive, it will create "/arn/
 A> archive" within the virtual folder, and then upload the
 A> whole virtual folder to the path you pointed it at which,
 A> in your case, is test1: (root of your hosting folder.

I'm getting that now. "rclone ls mycrypt: " reveals that it  
"knows" the directory path of the files in /arn/archive/  ..so,  
I can live with encrpyted dirs in the home root dir, no  
problem.

I'm really liking rclone.  Thanks for the heads up on it.  
Although it runs full throttle on a copy and sucks my upload  
bandwidth and thus affecting other things I need to do on the  
internet, I can schedule my backups/transfers to take place  
after hours.  OR.. I see that the --bwlimit might be a good  
option to employ to slow it down a notch.

What was not obvious at the start was that inorder to have a  
remote crypt type, it was a pre-requisite to have a standard  
remote type (ie. sftp) established.






-- 
  ../|ug

--- OpenXP 5.0.57
 * Origin: (} Pointy McPointface (618:250/1.9)