Fix faulty CRON_BACKUP_ONLY var warning logic.

This commit is contained in:
Aterfax 2024-03-26 23:09:41 +00:00
parent 756584639f
commit 9e239cc466
No known key found for this signature in database
GPG Key ID: 51E7ED3290C121FE

View File

@ -76,8 +76,8 @@ if [ "$CRON_BACKUP_ONLY" = "0" ] || [ -e "${lastrunfile}" ]; then
fi fi
elif [ "$CRON_BACKUP_ONLY" = "1" ]; then elif [ "$CRON_BACKUP_ONLY" = "1" ]; then
echo "CRON_BACKUP_ONLY=1, skipping container start up initial backup." echo "CRON_BACKUP_ONLY=1, skipping container start up initial backup."
elif [ "$CRON_BACKUP_ONLY" = "0" ] || [ "$CRON_BACKUP_ONLY" = "1" ] ]; then elif [ "$CRON_BACKUP_ONLY" != "0" ] && [ "$CRON_BACKUP_ONLY" != "1" ]; then
echo "CRON_BACKUP_ONLY set to invalid value, skipping container start up initial backup." echo "CRON_BACKUP_ONLY set to invalid value, skipping container start up initial backup."
fi fi
# Set this so backups always happen after the first run via CRON given logic above. # Set this so backups always happen after the first run via CRON given logic above.