summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2024-11-27 10:48:51 -0300
committerEuAndreh <eu@euandre.org>2024-11-27 10:48:54 -0300
commitfe3801ee1905129c8f3e1e1e0816fb86ac082143 (patch)
tree04f97852bbf58a2fcc3a7ae17fd03ef15c29a321
parentsrc/rc.sh: Add exported $MAKEFLAGS (diff)
downloadsyskeep-fe3801ee1905129c8f3e1e1e0816fb86ac082143.tar.gz
syskeep-fe3801ee1905129c8f3e1e1e0816fb86ac082143.tar.xz
src/check: Remove --verify-data from borg
The run-time of it is not compatible with the cronjob model. An improved version should use the cronjob to trigger the action by puttingit in a queue,and the cronjob itself would be finished. Asyynchronously a worker would consume the message and do the content verification, and at the end report the success or failure. A later cronjob at the end of the day could report the statuses of the events from the day.
-rwxr-xr-xsrc/check4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/check b/src/check
index 91bc153..12e3a86 100755
--- a/src/check
+++ b/src/check
@@ -26,10 +26,10 @@ btrfs: /dev/vda3 /dev/vdb1 /dev/vdc1
borg: borg-standby borg-offsite
borg-standby: ALWAYS
- env BORG_REPO=/mnt/backup/borg borg check --verbose --progress --verify-data
+ env BORG_REPO=/mnt/backup/borg borg check --verbose --progress
borg-offsite: ALWAYS
- borg check --verbose --progress --verify-data
+ borg check --verbose --progress
ALWAYS: