From 9e239cc466cb1752ab3228197b8c0167f5051d6f Mon Sep 17 00:00:00 2001
From: Aterfax <Aterfax@users.noreply.github.com>
Date: Tue, 26 Mar 2024 23:09:41 +0000
Subject: [PATCH] Fix faulty CRON_BACKUP_ONLY var warning logic.

---
 docker/src/s6-services/backup/run_include | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docker/src/s6-services/backup/run_include b/docker/src/s6-services/backup/run_include
index 13aeb46..cc536c1 100755
--- 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.