The installer names the unit this project packages #11

2026-09-14T12:11:36Z

jschoubben commented

2026-09-14 12:11:36 +00:00

The installer defaulted to mesh-host.service. What packaging/ ships is nox-mesh-host.service.

So on any real machine — one with the packaged unit installed and enabled — the installer would look for a unit that does not exist, and tell the operator that a real machine needs it installed. It was installed. Under the name the installer was not using.

Only the lab missed this, because the lab passes --host-in-background and never names a unit at all. Which is exactly the shape of thing that only shows up the first time somebody installs on a machine that matters.

The installer defaulted to `mesh-host.service`. What `packaging/` ships is `nox-mesh-host.service`. So on any real machine — one with the packaged unit installed and enabled — the installer would look for a unit that does not exist, and tell the operator that a real machine needs it installed. It was installed. Under the name the installer was not using. Only the lab missed this, because the lab passes `--host-in-background` and never names a unit at all. Which is exactly the shape of thing that only shows up the first time somebody installs on a machine that matters.

jschoubben added 1 commit 2026-09-14 12:11:36 +00:00

The installer names the unit this project packages cc9b3c1a8e

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.

jschoubben merged commit 0f143d16ce into main

2026-09-14 12:11:43 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#11