hernani/taler-monitoring
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix 1.23.2: max-ladder RUN_TIMEOUT 3h (not 600s from env)

Browse source 
Force MAX_LADDER_RUN_TIMEOUT/10800 in run-max-ladder-monitoring.sh so
shared ~/.config/taler-monitoring/env cannot shrink the daily hunt.
Install uses systemctl --no-block for long oneshots.
This commit is contained in:
Hernâni Marques 2026-07-19 15:15:04 +02:00
parent c1a3cba28b
commit bf04f90538
No known key found for this signature in database
4 changed files with 9 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

9
host-agent/install-host-agent.sh
View file

@ -88,11 +88,12 @@ install_local() {
systemctl --user daemon-reload 2>/dev/null || true
# initial stamp so path exists
"$ROOT/touch-software-stamp.sh"
systemctl --user start taler-monitoring-hacktivism.service || true
systemctl --user start taler-monitoring-surface.service || true
systemctl --user start taler-monitoring-aptdeploy.service || true
# oneshot jobs: --no-block so install does not wait hours
systemctl --user start --no-block taler-monitoring-hacktivism.service || true
systemctl --user start --no-block taler-monitoring-surface.service || true
systemctl --user start --no-block taler-monitoring-aptdeploy.service || true
# first max-ladder round immediately (daily thereafter)
systemctl --user start taler-monitoring-max-ladder.service || true
systemctl --user start --no-block taler-monitoring-max-ladder.service || true
echo "--- status ---"
systemctl --user status taler-monitoring-hacktivism.path --no-pager -l | head -15