novox/mesh-host
3
0
Fork 0
Code Issues Pull Requests 2 Releases Wiki Activity

The installer names the unit this project packages

Browse Source 
It defaulted to mesh-host.service. What packaging/ ships is nox-mesh-host.service,
so on any machine with the packaged unit installed the installer looked for
something absent and told the operator a real machine needs it installed — when
it was installed, under the name the installer was not using.

Only the lab missed it, because the lab passes --host-in-background and never
names a unit at all.
This commit is contained in:
jschoubben
2026-09-14 14:11:27 +02:00
parent 6205a93bfe
commit cc9b3c1a8e
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cmd/mesh-bootstrap/main.go
+4 -1
View File
@@ -42,7 +42,10 @@ const (
defaultOut = "/var/lib/mesh-host/substrate.lock" defaultOut = "/var/lib/mesh-host/substrate.lock"
defaultRegistry = "127.0.0.1:5000" defaultRegistry = "127.0.0.1:5000"
defaultHost = "/usr/local/bin/mesh-host" defaultHost = "/usr/local/bin/mesh-host"
defaultService = "mesh-host.service" // The unit this project actually packages, in `packaging/`. It said `mesh-host.service`, which
// is not a unit anybody installs — so on a machine with the packaged unit the installer looked
// for something absent, and told the operator a real machine needs it installed when it was.
defaultService = "nox-mesh-host.service"
) )
const usage = `mesh-bootstrap — make a bare machine into a mesh const usage = `mesh-bootstrap — make a bare machine into a mesh