-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support optional AXL configuration that deletes source files when transfer completes #74
Comments
I think should copy the behaviour of Source:
Dest:
So it looks like |
Hmm, "mv" should not have permission to run as root. What you probably are observing is the behavior of the file system, which is something beyond the control of mv. I think the most appropriate approach for AXL would be to emulate how web browsers are downloading files: create a temp name on the destination mount point, try to complete the transfer, if successful rename the file and remove the source. On failure, nobody will work with incomplete files at any point, a subsequent transfer of the same file can detect partial progress and resume (if temp names are not random) and garbage collection is also easy |
@bnicolae just for some context - the source files were owned by hutter2, but I was moving them to an ext4 mount that was owned by root (specifically, a file that I formatted ext4 and mounted loopback). So I just did a |
One potential future AXL user has requested the ability to have AXL automatically delete a source file after it has successfully transferred the file to its destination. This feature should be optional, since some users want to also keep the source files around.
An open question is how to handle the case where a transfer moves more than one file, and a subset of those succeed and others error out. Do we require an all or nothing when considering whether to delete the source files?
The text was updated successfully, but these errors were encountered: