In reference to your statement:
“
A refresh on the folder containing any local changes that you want to send to the cloud should trigger an immediate scan for odrive in that location (unless odrive is busy doing something else in another location), which should then send any “dirty” files to the remote storage.
”
Does this mean refresh can be used to delete files from a remote? or are “changed” files only files that exist and are modified? but I can’t sync a directory then sync all the files in it, then move those files away leaving the directory empty and then refresh that folder manually to delete it from the cloud? (I’d actually want this to happen, but it doubt it works this way? I assume refresh works about the same as killing the agent and restarting odrive? or rebooting and restarting odrive right?) not this alternate bizarre function I just made up? (I’ve never run a refresh command manually, and given what I just said, I’m slightly afraid to).
I didn’t see your edit here. You can use the shutdown command to stop the agent, and then launch the agent again when you want to resume. Is that what you are looking for?
Hi @bouya.daman,
A refresh is really just a manual way to tell odrive to look at the current folder and make sure the sync engine is up-to-date. For some integrations and configs odrive cannot see change events, so a change will not be picked up until odrive gets around to doing its periodic walk-and-check. A refresh will shortcut this on the target folder.
Deletes will be picked up in this case, and any local files that have been deleted in that folder will be picked-up and those delete actions will be held in the odrive trash until the user empties the odrive trash, which will sync those deletes to the remote storage.
This probably renders dozens of other questions I also just wrote irrelevant.
So I can simply delete a regular file (that odrive previously sync’d) then refresh the folder and then “empty trash” and then the file will be deleted from ACD as well?
That’s exactly how I wanted things to work. If true you can ignore all the other silly questions I wrote over at
That is correct.
After it sees the delete, the sync engine will hold on listing the delete in the trash queue for about 30 seconds, so just keep that in mind.
Didn’t even have to refresh, odrive was very quick about picking up on deleted files.
One comment though the emptytrash command could use feedback, my trash had/has 40,000 items in it, and I run emptytrash command and I see nothing, if I did something similar with sync I’d be getting spammed by lots of line by line information (which would assure me it was working).
Yes I can see the trash number shrinking by using the status command, but these 40,000 deletes might take all day so it would be nice if each delete triggered feedback in the command line. The deletes are going slow enough that next time I delete a migrated folder I might just delete files larger than 1MB, and let ACD remain polluted with a million tiny tiny files. heh.
edit: I wonder, it might just be faster to issue the delete command via ACD’s website, I think the reason odrive is deleting 40,000 files so slowly is throttling by ACD in regardless to api access
Hi @bouya.daman,
I agree, some feedback would be nice.
The odrive trash is a safety mechanism which prevent unintended deletes from hitting the remote storage, so Amazon doesn’t even know about the deletes until odrive sends them. That means that it has to be odrive that does it and there isn’t really a way to shortcut it… Once you clear the current queue it will at least be faster as you in-line the empty command.
Hi @bouya.daman,
I just meant adding the emptytrash command the trash as part of the overall script flow, so it is happening frequently as things are deleted.
