Gmer4Lfe f75957130e Cap merge-pass pull with the same 23h timeout as the main push ...

The pull step (merge mode) had no timeout or bandwidth limit at all,
so a slow/stalled pull could block the entire per-share sync
indefinitely — and since daily_sync_maintenance.sh calls rsync.sh
synchronously per share, that blocked every later share and all
post-sync maintenance jobs too. RSYNC_MAX_RUNTIME_HOURS was only ever
wired into the push half.

2026-07-14 18:29:53 -04:00

..

Manual-Rsync.md

Rename Lldap-Gmer4Lfe to Lldap and guard local containers in cleanup

2026-06-26 17:56:20 -04:00

README-Rsync.md

doc audit — fix stale watchdog vars, fallback_state_reset, add monthly_maintenance and mesh_monitor sections

2026-05-22 22:07:46 -04:00

rsync.sh

Cap merge-pass pull with the same 23h timeout as the main push

2026-07-14 18:29:53 -04:00