Skip to content

docs: socket guidance requires distinct paths, not merely explicit ones #104

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arcaven merged 1 commit into from
Aug 2, 2026
Merged

docs: socket guidance requires distinct paths, not merely explicit ones #104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading