-
Notifications
You must be signed in to change notification settings - Fork 78
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
Bugfix: Exit bitpocket when a rsync command fails #78
base: master
Are you sure you want to change the base?
Conversation
Ok, so I really like your idea. There's a possible security risk with the
Secondly, it requires extra space on the destination machine. Perhaps it should only be used for only the pull or push or both? If transferring large files, I could see where this might create problems? Thirdly, I think we may want to combine the idea with the |
Ok @greezybacon Is this what you had in mind? I implemented it only on the pull side, but the main point of the PR is to really exit in case of rsync error, which on my machines was not happening. |
OK @raphyduck I see your point with exiting based on rsync failures. I've opened #79 to handle that issue independently. Would you mind testing and giving an opinion? I don't like pork merges (where a PR includes stuff outside the scope of the PR -- eg. including #77), and I don't like merging a dozen unnecessary "mc" commits. So, I'll try rebasing and opening a separate PR for the transaction idea (with the --partial idea). |
Great thanks @greezybacon :) |
Also includes PR #77
Also uses the rsync option "--partial-dir", which is safe to use in case of network error but saves some bandwidth for error-prone network connections