acr-engine/scripts/start_wait_for_fma_guard.sh · 43644ac8006f0ff089a93a251e323b64dbe6dcf7 · wanghai-tech / hikoon-ACR · GitLab

Harden the FMA waiter by launching it as a real detached guard · d206f2c9 ...

Constraint: A multi-hour download needs a background guard that survives shell teardown, not just a logically correct polling loop.
Rejected: More ad-hoc nohup restarts | They obscured whether the issue was loop logic or process detachment.
Confidence: high
Scope-risk: narrow
Directive: Use the guard launcher for future unattended waits and keep pid/log artifacts so later sessions can verify liveness quickly.
Tested: Ran a foreground three-cycle control experiment, launched the new setsid-based guard, then verified the detached process survived with PPID 1 and emitted at least two polling cycles in the log.
Not-tested: Full handoff through completed download, extraction, and smoke still awaits archive completion.

authored 2026-06-02 14:07:53 +0800

start_wait_for_fma_guard.sh

303 Bytes

Raw
Blame
History
Permalink

#!/usr/bin/env bash
set -euo pipefail
cd "$(dirname "$0")/.."
LOG_FILE=".omx_wait_for_fma.log"
PID_FILE=".omx_wait_for_fma.pid"
: > "$LOG_FILE"
setsid /usr/local/miniconda3/bin/python -u scripts/wait_for_fma_and_prepare.py --interval 30 >> "$LOG_FILE" 2>&1 < /dev/null &
echo $! > "$PID_FILE"
echo "$!"