5 Commits

Include renames

Author	SHA1	Message	Date
jochen	66106d93ac	systemd: the journal verb reads a window, and failed is the seat's verb ... An incident is read for the minutes it happened in (the operator's direction 2026-10-07): journal takes since, until, priority and a fixed-string match. Every value is one word of journalctl's argv, held to the forms journalctl reads, so nothing reaches a shell or is read as an option under sudo. What the unit printed of a secret is redacted, as docker_logs does, before the match is applied, so a match cannot find one. systemd_failed becomes the seat's failed, with an optional scope. Needs the controller's seat with these verbs (mesh-controller, same branch): an older controller refuses a claim serving a verb its seat does not promise.	2026-10-07 19:15:20 +02:00
jochen	c42f1ce45b	systemd: port to Go, and read a system unit's journal as root ... The journal verb ran journalctl as the operator account, which outside the journal's group sees only its own entries: every system service read '-- No entries --', and a person reached for a shell. The read now escalates with sudo -n like the acts; ported to Go with every test. hq issue 255.	2026-10-05 18:09:42 +02:00
jochen	a80af7a97f	systemd owns its package; systemd-networkd configures networkd and claims none ... The service manager's package was declared by the networking module, so the module that is systemd could not own it and had to leave it out. networkd is a component of systemd: its module configures it. Removing the package resource from systemd-networkd uninstalls nothing — the host never removes a package that is not declared absent.	2026-10-04 12:17:08 +02:00
jochen	0596503db5	systemd: act as the runtime's account can, and never read a failure as an answer ... The node tools runtime runs as the operator account, not root, and gives its bundles no session words (novox/hq ADR 0175, 0188, 0193). So, per hq to-be 41 WP4: - system-scope start/stop/restart/enable/disable go through sudo -n when not root, as the packet filter and intrusion prevention do, and a refusal is named by how it failed; - user scope is plain --user with XDG_RUNTIME_DIR and the session bus of /run/user/<uid>; the dead --machine branches are gone; - a failed systemctl or journalctl is an error, and an unreachable user manager is said even when systemctl exits 0; systemd_failed reports it beside the other manager's answer instead of claiming nothing failed; - status says whether the mesh declares the unit: its loaded unit file begins with the header the host writes for a module's process. Only such a unit carries the restore note; - the package resource goes: the service manager is always present, and it collided with systemd-networkd's identical declaration; - calls are bounded below the runtime's call limit, a unit name is never an option, and the runner is injected so the tests use a fake one.	2026-10-04 03:58:19 +02:00
jochen	a1d7b9ad5a	systemd: the service manager as a module — holds node-service-manager and answers for the units in both scopes ... The holder of the seat the controller seeds under novox/hq ADR 0177. Eight verbs under the seat's name — units, status, start, stop, restart, enable, disable, journal — each taking an optional scope, "system" by default or "user" for the operator account's own manager, reached as `systemctl --user --machine=<account>@` when the runtime is not that account. One tool of its own, systemd_failed, for every failed unit in both scopes. A package, a claim and a bundle; no container, no process: served by the node tools runtime (ADR 0175) once it exists. `module check` passes against a controller that carries the seat; the tools type-check against the SDK.	2026-10-04 02:32:34 +02:00