From 19ba1e723cca99bd03a1373f2608b8b2dac80076 Mon Sep 17 00:00:00 2001 From: Gmer4Lfe Date: Sun, 16 Aug 2026 13:13:25 -0400 Subject: [PATCH] Stop a paused rsync counting as an absent partner and auto-offboarding the partnership --- Orchestrators/critical_sync_maintenance.sh | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/Orchestrators/critical_sync_maintenance.sh b/Orchestrators/critical_sync_maintenance.sh index 83adfd8..99ca7b3 100755 --- a/Orchestrators/critical_sync_maintenance.sh +++ b/Orchestrators/critical_sync_maintenance.sh @@ -244,9 +244,19 @@ if [[ "${PARTNERSHIP_ENABLED:-false}" == true ]]; then PARTNER_DRY="" [[ "$DRY_RUN" == true ]] && PARTNER_DRY="--dry-run" + # A successful rsync proves the partner answered; a failed one is evidence it did not. But + # rsync being switched off is neither — and it used to be read as "unseen", so the offline + # counter climbed every 30 minutes toward the 30-day auto-offboard on a partnership whose + # only fault was that RSYNC_ENABLED=false. That is how a deliberately paused sync ends up + # dismantling the partnership it was paused for. With no rsync attempt there is nothing to + # report, so the check runs without touching the counter either way. if [[ "$RSYNC_OK" == true ]]; then bash "$SCRIPT_DIR/../Partnership/partnership_manager.sh" \ --check --remote-seen $PARTNER_DRY + elif [[ "${RSYNC_ENABLED:-false}" != true ]]; then + echo "Rsync disabled — partnership check runs, offline counter untouched" + bash "$SCRIPT_DIR/../Partnership/partnership_manager.sh" \ + --check $PARTNER_DRY else bash "$SCRIPT_DIR/../Partnership/partnership_manager.sh" \ --check --remote-unseen $PARTNER_DRY