Fix faulty CRON_BACKUP_ONLY var warning logic.

Aterfax · Mar 26, 2024 · 9e239cc · 9e239cc
1 parent 7565846
commit 9e239cc
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docker/src/s6-services/backup/run_include b/docker/src/s6-services/backup/run_include
@@ -76,8 +76,8 @@ if [ "$CRON_BACKUP_ONLY" = "0" ] || [ -e "${lastrunfile}" ]; then
     fi
 elif [ "$CRON_BACKUP_ONLY" = "1" ]; then
     echo "CRON_BACKUP_ONLY=1, skipping container start up initial backup."
-elif [ "$CRON_BACKUP_ONLY" = "0" ] || [ "$CRON_BACKUP_ONLY" = "1" ] ]; then 
-echo "CRON_BACKUP_ONLY set to invalid value, skipping container start up initial backup."
+elif [ "$CRON_BACKUP_ONLY" != "0" ] && [ "$CRON_BACKUP_ONLY" != "1" ]; then 
+    echo "CRON_BACKUP_ONLY set to invalid value, skipping container start up initial backup."
 fi
 
 # Set this so backups always happen after the first run via CRON given logic above.