Fixes the control-node's agent account never being judged ("not judged (search incomplete): the search for setuid programs did not finish within 15m0s"), which keeps the router refusing to link a channel there.
What changes (internal/accounts, rootsearch):
No bound on the search. The walk is the engine's own (filepath.WalkDir per filesystem, staying on its device like find -xdev, same prunes, same match, never following a link), in lexical order, so its progress is one cursor per filesystem.
Resumable: the progress is kept every minute in setuid-search-progress.json beside the engine's state (written to a new file and renamed; read only as a regular file, no link followed, owned by the engine's account and writable by it alone, in a directory that is the same). An engine restarted, updated or rebooted carries the walk on from its cursor; a walk older than rootsearch.FreshFor, or one an apply asked to redo, starts over.
Low priority, one at a time: the walk runs on a goroutine locked to its own thread, set to nice 19 and the idle I/O class (per thread on Linux; the thread ends with the goroutine). The package manager is asked through Idle (same, plus the parent-death signal). A priority that cannot be lowered fails the search instead of walking at full priority.
Verdict only from a complete search younger than rootsearch.FreshFor (36 h = Every 24 h + Quiet 12 h), dated by its start, kept in setuid-search.json so a restart judges from it. Before one completes, or once it is too old: not judged yet (search running); after a failure: not judged (search incomplete). Never free from an incomplete or stale search.
A new search daily, after an apply whose outcomes moved a user, a package, an action or a file under the user/group databases or sudo/doas/polkit rules (apply.MovesRoot), and when a filesystem appears that the last one did not walk (at most once an hour for the last two).
rootsearch.Bound is gone; rootsearch.Every, FreshFor and Quiet replace it. The controller's pull request reads Quiet.
Soundness: only root can make a setuid- or setgid-root file, never the agent account, so a complete search stays sound until root acts, and root's acts through the mesh start a new search. A file appearing behind the cursor of a running walk was made by root.
Tests: completion without a deadline; verdict from the cached complete search, also after a restart; stale -> pending, never free; incomplete never free (also with a stale result behind it); re-search after an apply that moved root; the walk finds setuid/setgid files and follows no link; an unreadable directory is an incomplete walk; an interrupted walk carries on from its cursor (a file added before the cursor is not walked, one after it is); a walk too old or asked again starts over; a kept file that is a link, writable by others or in a directory writable by others is not read; the idle runner runs at nice 19. merge-check.sh passes locally (no bus here).
The controller's pull request (mesh-controller, same branch name) pins this commit.
Fixes the control-node's agent account never being judged ("not judged (search incomplete): the search for setuid programs did not finish within 15m0s"), which keeps the router refusing to link a channel there.
**What changes (internal/accounts, rootsearch):**
- No bound on the search. The walk is the engine's own (filepath.WalkDir per filesystem, staying on its device like `find -xdev`, same prunes, same match, never following a link), in lexical order, so its progress is one cursor per filesystem.
- Resumable: the progress is kept every minute in `setuid-search-progress.json` beside the engine's state (written to a new file and renamed; read only as a regular file, no link followed, owned by the engine's account and writable by it alone, in a directory that is the same). An engine restarted, updated or rebooted carries the walk on from its cursor; a walk older than `rootsearch.FreshFor`, or one an apply asked to redo, starts over.
- Low priority, one at a time: the walk runs on a goroutine locked to its own thread, set to nice 19 and the idle I/O class (per thread on Linux; the thread ends with the goroutine). The package manager is asked through `Idle` (same, plus the parent-death signal). A priority that cannot be lowered fails the search instead of walking at full priority.
- Verdict only from a complete search younger than `rootsearch.FreshFor` (36 h = `Every` 24 h + `Quiet` 12 h), dated by its start, kept in `setuid-search.json` so a restart judges from it. Before one completes, or once it is too old: `not judged yet (search running)`; after a failure: `not judged (search incomplete)`. Never free from an incomplete or stale search.
- A new search daily, after an apply whose outcomes moved a user, a package, an action or a file under the user/group databases or sudo/doas/polkit rules (`apply.MovesRoot`), and when a filesystem appears that the last one did not walk (at most once an hour for the last two).
- `rootsearch.Bound` is gone; `rootsearch.Every`, `FreshFor` and `Quiet` replace it. The controller's pull request reads `Quiet`.
**Soundness:** only root can make a setuid- or setgid-root file, never the agent account, so a complete search stays sound until root acts, and root's acts through the mesh start a new search. A file appearing behind the cursor of a running walk was made by root.
**Tests:** completion without a deadline; verdict from the cached complete search, also after a restart; stale -> pending, never free; incomplete never free (also with a stale result behind it); re-search after an apply that moved root; the walk finds setuid/setgid files and follows no link; an unreadable directory is an incomplete walk; an interrupted walk carries on from its cursor (a file added before the cursor is not walked, one after it is); a walk too old or asked again starts over; a kept file that is a link, writable by others or in a directory writable by others is not read; the idle runner runs at nice 19. `merge-check.sh` passes locally (no bus here).
The controller's pull request (mesh-controller, same branch name) pins this commit.
A machine with millions of files never finished the walk within fifteen
minutes, so its agent account was never judged and the router refused to
link. Only root can make a setuid-root file, so a complete search stays
sound until root acts: it now runs at idle priority with no bound, is kept
beside the engine's state, judges for rootsearch.FreshFor from its start,
runs again daily and after an apply that moves accounts, packages, actions
or sudo rules, and an incomplete or stale search is never free.
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
The control-node's walk takes far longer than the engine runs between
updates, so a search that starts over at every restart never completes.
The walk is the engine's own, in lexical order, so its progress is one
cursor per filesystem, kept every minute beside the engine's state and
carried on after a restart while younger than rootsearch.FreshFor. It runs
on a thread of its own at nice 19 and the idle I/O class.
composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
Machines
mesh-host on ace: passed — healthy 3 times over 2m48s
mesh-host on g14: passed — carried by plan-1791584475080493383
mesh-host on the rest running it: sent
Transitions
2026-10-09 23:11 (new) → proposed (announced): novox/mesh-host#75's head announced
2026-10-09 23:13 proposed → checked (checked): the verdict names this commit
2026-10-09 23:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 23:19 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 23:19 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
2026-10-09 23:27 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-host@a7270f00cbe0` — **delivered** since 2026-10-09T23:27:31Z
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
**Group** `fix/361-the-setuid-search-runs-to-completion`, in order: novox/mesh-controller@9551bc23809d → novox/mesh-host@a7270f00cbe0
- novox/mesh-controller@9551bc23809d before novox/mesh-host@a7270f00cbe0: built by, over engine before controller
- composed together: pass — every machine composes with the change as it did without (4 of 4 compose)
**Machines**
- mesh-host on ace: passed — healthy 3 times over 2m48s
- mesh-host on g14: passed — carried by plan-1791584475080493383
- mesh-host on the rest running it: sent
**Transitions**
- 2026-10-09 23:11 (new) → proposed (announced): novox/mesh-host#75's head announced
- 2026-10-09 23:13 proposed → checked (checked): the verdict names this commit
- 2026-10-09 23:13 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 23:19 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 23:19 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path
- 2026-10-09 23:27 delivering → delivered (done): its walk is done: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Run by the build seat on shanks as build-1791586922602162763 (builds --log build-1791586922602162763).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:34:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T22:34:01Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s
ok github.com/novox/mesh-host/cmd/mesh-host 5.520s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.439s
ok github.com/novox/mesh-host/internal/apply 4.795s
ok github.com/novox/mesh-host/internal/bootstrap 1.660s
ok github.com/novox/mesh-host/internal/bundle 1.034s
ok github.com/novox/mesh-host/internal/declaration 1.087s
ok github.com/novox/mesh-host/internal/firewall 1.857s
ok github.com/novox/mesh-host/internal/identity 1.175s
ok github.com/novox/mesh-host/internal/image 1.043s
ok github.com/novox/mesh-host/internal/inventory 1.044s
ok github.com/novox/mesh-host/internal/link 10.465s
ok github.com/novox/mesh-host/internal/liveness 2.138s
ok github.com/novox/mesh-host/internal/meshcli 1.362s
ok github.com/novox/mesh-host/internal/network 1.103s
ok github.com/novox/mesh-host/internal/outward 1.046s
ok github.com/novox/mesh-host/internal/profile 1.536s
ok github.com/novox/mesh-host/internal/reachable 1.041s
ok github.com/novox/mesh-host/internal/store 1.274s
ok github.com/novox/mesh-host/internal/system 1.048s
ok github.com/novox/mesh-host/internal/tunnel 1.047s
ok github.com/novox/mesh-host/internal/units 1.043s
ok github.com/novox/mesh-host/internal/upgrade 1.228s
ok github.com/novox/mesh-host/internal/witness 4.865s
ok github.com/novox/mesh-host/packaging 1.036s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.040s
**Merge check** at `2dbbda51`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
Run by the build seat on shanks as `build-1791586922602162763` (`builds --log build-1791586922602162763`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:34:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T22:34:01Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.014s
ok github.com/novox/mesh-host/cmd/mesh-host 5.520s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.439s
ok github.com/novox/mesh-host/internal/apply 4.795s
ok github.com/novox/mesh-host/internal/bootstrap 1.660s
ok github.com/novox/mesh-host/internal/bundle 1.034s
ok github.com/novox/mesh-host/internal/declaration 1.087s
ok github.com/novox/mesh-host/internal/firewall 1.857s
ok github.com/novox/mesh-host/internal/identity 1.175s
ok github.com/novox/mesh-host/internal/image 1.043s
ok github.com/novox/mesh-host/internal/inventory 1.044s
ok github.com/novox/mesh-host/internal/link 10.465s
ok github.com/novox/mesh-host/internal/liveness 2.138s
ok github.com/novox/mesh-host/internal/meshcli 1.362s
ok github.com/novox/mesh-host/internal/network 1.103s
ok github.com/novox/mesh-host/internal/outward 1.046s
ok github.com/novox/mesh-host/internal/profile 1.536s
ok github.com/novox/mesh-host/internal/reachable 1.041s
ok github.com/novox/mesh-host/internal/store 1.274s
ok github.com/novox/mesh-host/internal/system 1.048s
ok github.com/novox/mesh-host/internal/tunnel 1.047s
ok github.com/novox/mesh-host/internal/units 1.043s
ok github.com/novox/mesh-host/internal/upgrade 1.228s
ok github.com/novox/mesh-host/internal/witness 4.865s
ok github.com/novox/mesh-host/packaging 1.036s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.040s
```
mesh/merge-gate pass: builds mesh-host → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without (4 of 4 compose)
The review found a cursor of a name that is not UTF-8 came back changed
from JSON, so a resumed walk skipped what it stood before; an ask to
search again was lost to a restart, which carried the older walk on; a
fresh search judged a filesystem it never walked; a mount point root
cannot read failed or hung the walk; a found file gone before the package
manager was asked failed every resume; and skipped or kept outcomes
started a search on every reconcile, back to back with a long walk.
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host
Run by the build seat on shanks as build-1791587468619744117 (builds --log build-1791587468619744117).
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:34:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T22:34:01Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.015s
ok github.com/novox/mesh-host/cmd/mesh-host 5.569s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.501s
ok github.com/novox/mesh-host/internal/apply 4.784s
ok github.com/novox/mesh-host/internal/bootstrap 1.660s
ok github.com/novox/mesh-host/internal/bundle 1.044s
ok github.com/novox/mesh-host/internal/declaration 1.084s
ok github.com/novox/mesh-host/internal/firewall 1.859s
ok github.com/novox/mesh-host/internal/identity 1.187s
ok github.com/novox/mesh-host/internal/image 1.035s
ok github.com/novox/mesh-host/internal/inventory 1.042s
ok github.com/novox/mesh-host/internal/link 10.447s
ok github.com/novox/mesh-host/internal/liveness 2.147s
ok github.com/novox/mesh-host/internal/meshcli 1.363s
ok github.com/novox/mesh-host/internal/network 1.105s
ok github.com/novox/mesh-host/internal/outward 1.043s
ok github.com/novox/mesh-host/internal/profile 1.536s
ok github.com/novox/mesh-host/internal/reachable 1.040s
ok github.com/novox/mesh-host/internal/store 1.283s
ok github.com/novox/mesh-host/internal/system 1.047s
ok github.com/novox/mesh-host/internal/tunnel 1.052s
ok github.com/novox/mesh-host/internal/units 1.038s
ok github.com/novox/mesh-host/internal/upgrade 1.242s
ok github.com/novox/mesh-host/internal/witness 4.824s
ok github.com/novox/mesh-host/packaging 1.044s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.040s
**Merge check** at `a7270f00`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step
- tier 0: mesh-host
- ace: receives mesh-host
- g14: receives mesh-host
- novox: receives mesh-host
- shanks: receives mesh-host
Run by the build seat on shanks as `build-1791587468619744117` (`builds --log build-1791587468619744117`).
```
--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-09T22:34:01Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-09T22:34:01Z
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 1 module(s) in 1 tier(s): mesh-host
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.015s
ok github.com/novox/mesh-host/cmd/mesh-host 5.569s
ok github.com/novox/mesh-host/examples 1.020s
ok github.com/novox/mesh-host/internal/accounts 1.501s
ok github.com/novox/mesh-host/internal/apply 4.784s
ok github.com/novox/mesh-host/internal/bootstrap 1.660s
ok github.com/novox/mesh-host/internal/bundle 1.044s
ok github.com/novox/mesh-host/internal/declaration 1.084s
ok github.com/novox/mesh-host/internal/firewall 1.859s
ok github.com/novox/mesh-host/internal/identity 1.187s
ok github.com/novox/mesh-host/internal/image 1.035s
ok github.com/novox/mesh-host/internal/inventory 1.042s
ok github.com/novox/mesh-host/internal/link 10.447s
ok github.com/novox/mesh-host/internal/liveness 2.147s
ok github.com/novox/mesh-host/internal/meshcli 1.363s
ok github.com/novox/mesh-host/internal/network 1.105s
ok github.com/novox/mesh-host/internal/outward 1.043s
ok github.com/novox/mesh-host/internal/profile 1.536s
ok github.com/novox/mesh-host/internal/reachable 1.040s
ok github.com/novox/mesh-host/internal/store 1.283s
ok github.com/novox/mesh-host/internal/system 1.047s
ok github.com/novox/mesh-host/internal/tunnel 1.052s
ok github.com/novox/mesh-host/internal/units 1.038s
ok github.com/novox/mesh-host/internal/upgrade 1.242s
ok github.com/novox/mesh-host/internal/witness 4.824s
ok github.com/novox/mesh-host/packaging 1.044s
? github.com/novox/mesh-host/rootsearch [no test files]
ok github.com/novox/mesh-host/validate 1.040s
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes the control-node's agent account never being judged ("not judged (search incomplete): the search for setuid programs did not finish within 15m0s"), which keeps the router refusing to link a channel there.
What changes (internal/accounts, rootsearch):
find -xdev, same prunes, same match, never following a link), in lexical order, so its progress is one cursor per filesystem.setuid-search-progress.jsonbeside the engine's state (written to a new file and renamed; read only as a regular file, no link followed, owned by the engine's account and writable by it alone, in a directory that is the same). An engine restarted, updated or rebooted carries the walk on from its cursor; a walk older thanrootsearch.FreshFor, or one an apply asked to redo, starts over.Idle(same, plus the parent-death signal). A priority that cannot be lowered fails the search instead of walking at full priority.rootsearch.FreshFor(36 h =Every24 h +Quiet12 h), dated by its start, kept insetuid-search.jsonso a restart judges from it. Before one completes, or once it is too old:not judged yet (search running); after a failure:not judged (search incomplete). Never free from an incomplete or stale search.apply.MovesRoot), and when a filesystem appears that the last one did not walk (at most once an hour for the last two).rootsearch.Boundis gone;rootsearch.Every,FreshForandQuietreplace it. The controller's pull request readsQuiet.Soundness: only root can make a setuid- or setgid-root file, never the agent account, so a complete search stays sound until root acts, and root's acts through the mesh start a new search. A file appearing behind the cursor of a running walk was made by root.
Tests: completion without a deadline; verdict from the cached complete search, also after a restart; stale -> pending, never free; incomplete never free (also with a stale result behind it); re-search after an apply that moved root; the walk finds setuid/setgid files and follows no link; an unreadable directory is an incomplete walk; an interrupted walk carries on from its cursor (a file added before the cursor is not walked, one after it is); a walk too old or asked again starts over; a kept file that is a link, writable by others or in a directory writable by others is not read; the idle runner runs at nice 19.
merge-check.shpasses locally (no bus here).The controller's pull request (mesh-controller, same branch name) pins this commit.
Delivery
novox/mesh-host@a7270f00cbe0— delivered since 2026-10-09T23:27:31ZDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Group
fix/361-the-setuid-search-runs-to-completion, in order: novox/mesh-controller@9551bc2380 → novox/mesh-host@a7270f00cbMachines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
2dbbda51mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791586922602162763(builds --log build-1791586922602162763).Merge check at
a7270f00mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791587468619744117(builds --log build-1791587468619744117).