Run the download orphan cleaner daily — a weekly batch of newly-eligible orphans can exceed the delete cap, which aborts the whole pass and rolls the backlog into an even larger next run

This commit is contained in:
Gmer4Lfe
2026-07-27 17:24:40 -04:00
parent 7505bffcee
commit 74ea1a5218
2 changed files with 9 additions and 3 deletions
+4 -2
View File
@@ -59,7 +59,7 @@
# USAGE
# ==============================================================================================
#
# arr_download_orphan_cleaner.sh — weekly orchestrator entry
# arr_download_orphan_cleaner.sh — daily orchestrator entry
# arr_download_orphan_cleaner.sh --dry-run — classify and report only
# arr_download_orphan_cleaner.sh --status — show config and exit
# arr_download_orphan_cleaner.sh --i-know-what-im-doing — bypass MAX_DELETE_GB cap
@@ -293,7 +293,9 @@ echo "$ICON_TRASH Deleted: $TOTAL_DELETED ($((TOTAL_DELETED_MB / 1024))G
echo "$ICON_RUN Import scans: $TOTAL_SCANS"
echo "$ICON_WARN Held: $TOTAL_HELD"
if [[ "$DRY_RUN" != true ]] && (( TOTAL_DELETED > 0 || TOTAL_HELD > 0 )); then
# Held alone never notifies — there is always something awaiting review, and on a daily
# schedule that would be a notification every morning saying nothing happened.
if [[ "$DRY_RUN" != true ]] && (( TOTAL_DELETED > 0 )); then
notify "Download orphan cleaner on $(hostname): deleted $TOTAL_DELETED orphans ($((TOTAL_DELETED_MB / 1024))G), triggered $TOTAL_SCANS import scans, $TOTAL_HELD held for review" \
"Download Orphan Cleaner" "normal"
fi