Tolerence for temp files in filesystem for backups #1726
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Can you add a video testing this @znowfox ? |
Author
|
Again, when i run all the steps from the js file one by one, the zip cmd issues the warning that some files it was going to store aren't present anymore (rapid firing temp/lock files) ignoring them by targeting them won't make it exhaustive i think, for other cases aswell. You might wanna remove the dev null? Catch the zip output aswell. |
Author
Contributor
|
@znowfox |
Contributor
|
Fix in #1823 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backups will ALWAYS fail with posteio running (or others really), too many rapidly fading temp files --
adding tolerance for some 0 byte skipped files.