From 611ee856c53f9beee52f807c9134b232e4e83977 Mon Sep 17 00:00:00 2001 From: gkd2323c Date: Fri, 4 Sep 2026 01:22:21 +0800 Subject: [PATCH] fix(process): drop OOMPolicy from systemd-run --scope argv OOMPolicy is a service-unit property; systemd-run --user --scope rejects it with 'Unknown assignment: OOMPolicy=kill'. The availability probe therefore always failed in supervised Linux gateways, making restart-safe cron worker dispatch (systemd scope) permanently unavailable and falling back to in-cgroup workers. MemoryMax + MemoryAccounting remain; OOMPolicy adds nothing for a transient scope (no service manager to act on the OOM event). --- tools/process_registry.py | 1 - 1 file changed, 1 deletion(-) diff --git a/tools/process_registry.py b/tools/process_registry.py index afdd52a0e7..474f97e39e 100644 --- a/tools/process_registry.py +++ b/tools/process_registry.py @@ -131,7 +131,6 @@ def _systemd_scope_argv(binary: str, unit_name: str, *argv: str) -> List[str]: binary, "--user", "--scope", "--quiet", "--unit", unit_name, "--collect", "--property", "MemoryAccounting=yes", "--property", f"MemoryMax={_worker_memory_max_bytes()}", - "--property", "OOMPolicy=kill", "--", *argv, ]