855b7a6e30ead43cce1936a7cb381d783f9fad00
bmc_monitor.sh was doing two unrelated jobs: sampling `free -m` every few seconds, and running `memtester 500M 1` as a stress load. They want different timeouts -- a monitor should give up in 30 s, a memtester pass legitimately runs for minutes -- and mixing them meant either cutting memtester short or letting a hung sample stall the loop. bmc_monitor.sh now polls `free -m` only, keeping CMD_TIMEOUT_SEC=30. bmc_monitor_ddr.sh is the stress half: memtester only, with CMD_TIMEOUT_SEC raised to 3600. The two are otherwise identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014RetWKFZFG1ZHcitQAyhwM
Description
Blanton Tera Term TTL reliability test
4.2 MiB