1.24.16 — Unambiguous cron Jobman startup
Editorial identity incomplete
2026-09-09
Cron now invokes the installed Jobman module through a stable bash → Jobman → engine process chain. MojoSec can prove scheduled firewall work after deployments without treating the legitimate wrapper re-exec sequence as unexplained privileged activity. No migrations or configuration changes are required.
Fixed
- API deploys now install and preflight a direct system-Python Jobman cron command, giving the cron shell, Jobman, and the restarted engine distinct Audit identities.
- MojoSec matches that same generated command, so fully proven firewall broker work stays local instead of flooding the central security stream.
Upgrade notes
- Deploy normally. The API deployment replaces the jobs cron entry, retires the old engine and scheduler, and lets the next cron tick start the replacements.