Docs: mention the behavior of "sync" cron job in case of "warnings" #340
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.
The recommended cron job command for
sync_first 1
behaves differently than the non-sync command recommendation:sync_first 0
: "warnings" occurring during the rsync operation do not influence the following "rotate" operationsync_first 1
: "warnings" during "rsnaphot sync" lead to an exit code value 2. The rotation is skipped (rsnapshot sync && rsnapshot alpha
).Now the man page mentions this difference in behavior and recommends an adjusted cron job, which preserves the non-sync behavior.
See #338