From 21eb3c3f94da4d8c6ff949cba19f2529e3c1f7f9 Mon Sep 17 00:00:00 2001 From: Michael Pursifull Date: Sat, 1 Aug 2026 20:00:42 -0500 Subject: [PATCH] docs: socket guidance requires distinct paths, not merely explicit ones Two daemons handed the same explicit --socket path collide exactly as they do on the default; distinctness is the property that matters. Observed live during the d0pt investigation when two agents were prescribed the same scratch path. Refs: aae-orc-t6da --- docs/architecture.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/architecture.md b/docs/architecture.md index 91e8086..a1857f2 100644 --- a/docs/architecture.md +++ b/docs/architecture.md @@ -174,8 +174,10 @@ and it is machine-global: no environment variable moves it, and neither does HOME. A starting daemon unlinks whatever is at its socket path without checking for a live owner, so a second daemon on that path takes new client connections while the first keeps running with no reachable path, and either -one's shutdown unlinks the path. Run concurrent daemons on a host with one -`--socket` each, and pass the same value to every client command. +one's shutdown unlinks the path. Give each concurrent daemon on a host its +own distinct `--socket` path and pass that path to every client command +aimed at it. Two daemons handed the same explicit path collide exactly as +they do on the default. ### Cluster configuration