A job killed hard never corrects its own record, so 'running' outlives the process and the pid can since belong to something else; array-start jobs get setsid too, so Stop can reach past their direct children.
The Custom/ prefix is a namespace, not a directory under SCRIPTS_DIR, so every launcher that resolved it as one could never find the script.
- FallBack tab: per-node tier inventory + active fallback card with duration, tier, handback strikes, running container status - Watchdog tab: live system health (RAM bar + thresholds, load, uptime, daemon), docker watchdog strikes + skip list + restart history, stability strikes + reboot log, resource pressure alert card, config inventory (mem limits, required, pause/stop lists) - Swapped partnership/arrs tab order; FallBack between partnership and watchdog - Plugin source tree moved from Plugin/usr/local/emhttp/plugins/varaverk/ to Plugin/unraid/ - Deployment/ conf templates added
Gmer4Lfe