systemd-resolved: say when a route's domains do cross the bus
mesh/merge-gate pass: builds new: modules/systemd-resolved, sent nowhere; no bus step; every machine composes with the change as it did without (4 of 4 com…
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery held for a person: merged, and the controller opened no walk for it within 10m0s — nothing it holds follows that branch, or the merge was…
mesh/merge-gate pass: builds new: modules/systemd-resolved, sent nowhere; no bus step; every machine composes with the change as it did without (4 of 4 com…
mesh/repo-check pass: its merge-check.sh passed
mesh/delivery held for a person: merged, and the controller opened no walk for it within 10m0s — nothing it holds follows that branch, or the merge was…
This commit is contained in:
@@ -71,7 +71,8 @@ same three, plus:
|
||||
- `route` with `takes` (the write's `id`) and `by` (the module's name): route, then take that write, so
|
||||
the module's file is put back.
|
||||
|
||||
A VPN's servers and domains go over this socket and never over the bus, so they never leave the machine.
|
||||
A VPN's servers and domains are handed over on this socket, never over the bus. They cross the bus only
|
||||
as the answer to `routes` when the operator asks it, and nothing keeps that answer.
|
||||
|
||||
resolved holds the routes itself, per link, and forgets a link's route when the link goes. Nothing here
|
||||
keeps a table of its own that could disagree with it.
|
||||
|
||||
Reference in New Issue
Block a user