This is important to us because we create empty directories which are used randomly as needed by software products on the server. If they are not there, the software fails.
Is this a flaw or if known, is there any plan to incorporate these ?
Here is an example of the rclone command we are using where this behavior is present:
rclone copy --log-file /CM/data-drive/logs/backup-offsite.log --config /CM/data-drive/cm_backups/offsite/rclone.conf /CM/data-drive data-drive:$bucket_id
I feel you might be misunderstanding the question. My goal is to create them not delete them. So I am uncertain about your last line to “delete them after”.
What I was saying is that rclone won’t create EMPTY directories in the destination. It only creates files which implicately then create the directories those files are contained in.
My suggestion was to touch files in the empty directories locally before syncing, then remove those files that you created. Like this in bash:
Ah - That cleared it up. Good potential work around. I’ll create a bash script that puts an empty file in all directories prior to running. That’s a good work around.
May nee to tweak that a little. There may be issues with zero bytes files. I’d change that bash script to put small files (maybe echo > deleteme.txt) rather than a zero byte. I just looking at my script…