#!/bin/bash
# chain5.sh — F14 settled by measurement: OpenGist on the LIVE template (128M) once more, with the cgroup's
# memory.events and swap sampled every 3 s by tools/memprobe-guest.sh inside the guest. The drill-2 run is kept as
# run-drill-2. Question: does 128M reach its limit (events max/oom_kill) or push the app into swap?
E=/mnt/5_hdd/felhom.eu/git/felhom.eu/documentation/audits/catalog-sweep-2026-10-24
export SC=/run/user/1000/sweep-sc TARGET=sweep BASE=https://192.168.0.157 DRIVE_ROOT=/mnt/felhom-drives/hdd_1 SWEEP_EV=$E
cd $E/tools
keep_first() { a=$1; if [ -d "$E/$a" ] && [ ! -d "$E/$a/run-$2" ]; then mkdir -p "$E/$a/run-$2"; find "$E/$a" -maxdepth 1 -mindepth 1 ! -name 'first-run' ! -name 'run-*' -exec mv {} "$E/$a/run-$2/" \; ; fi; }
G() { ssh -n -o BatchMode=yes root@192.168.0.138 "pct exec 9201 -- bash -c \"$1\""; }
grep -q 'app-catalog-felhom.eu' <(G "grep repo_url /var/lib/docker/volumes/felhom-controller-data/_data/controller.yaml") || { echo "$(date -u +%T) WARN chain5: box not on live — nothing done" >> $E/progress.log; exit 1; }
keep_first opengist drill-2
G "rm -f /root/mp-opengist.txt; nohup /root/memprobe-guest.sh opengist /root/mp-opengist.txt 600 >/dev/null 2>&1 &"
echo "$(date -u +%T) START memprobe opengist (live 128M)" >> $E/progress.log
timeout 2700 python3 sweep.py opengist > $E/opengist.console.txt 2>&1 < /dev/null
rc=$?
sleep 10
G "cat /root/mp-opengist.txt" > $E/opengist/memprobe-128M.txt
echo "$(date -u +%T) END memprobe opengist rc=$rc ($(wc -l < $E/opengist/memprobe-128M.txt) samples); CHAIN5 DONE" >> $E/progress.log