docs: connection model documents the machine-global default socket - #103
Merged
Conversation
The local socket default is the hardcoded config.DefaultSocket (/tmp/marvel.sock) on both the daemon and every client; no environment variable moves it and neither does HOME (paths.RuntimeSocket reads XDG_RUNTIME_DIR but has no callers). A starting daemon unlinks the path without a liveness probe, so a second daemon silently takes new connections while the first keeps running unreachable. Documented with the --socket guidance for concurrent daemons; behavior itself tracked as aae-orc-t6da. Also rewraps the event-ring paragraph left ragged by #100. Refs: aae-orc-t6da
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two agents debugging on one host just lost forty minutes to this: marvel's local socket default is the literal
/tmp/marvel.sockon both the daemon and every client, a starting daemon unlinks the path without checking for a live owner, and the displaced daemon keeps running with no reachable path. The connection-model section now states the resolution (hardcoded constant; no environment variable moves it, HOME does not either), the last-binder-wins mechanism, and the operational guidance: one--socketper concurrent daemon, same value on every client command. Every clause is code-verified (config.DefaultSocket, the unlink at daemon startup, the shutdown unlink;paths.RuntimeSocketreads XDG_RUNTIME_DIR but nothing calls it). The behavior itself is tracked as aae-orc-t6da; this documents what ships today. Also rewraps the event-ring paragraph left ragged by #100.Refs: aae-orc-t6da