mesh-mail-notifier: the watcher runs in the base invocation, not a separate notify process (issue 859)

The notify process's stdin is empty under systemd, so stdio.Serve returned at EOF, main returned, and
systemd restarted it every five seconds: the watch loop never ran long enough to show a notice. The watch
loop now starts beside stdio.Serve in the one process the node's runtime launches and keeps alive, as
mesh-knowledge's serve does. No resource declares a separate notify process any more.
This commit is contained in:
jochen
2026-10-15 23:13:34 +02:00
parent c9848f4fb8
commit 12d7852082
5 changed files with 109 additions and 27 deletions
-13
View File
@@ -47,19 +47,6 @@
"mode": "0700",
"owner": "mesh-mail-notifier",
"place": "."
},
{
"id": "notify",
"type": "process",
"name": "mesh-mail-notifier-notify",
"artifact": "tools",
"run": [
"./mesh-mail-notifier",
"notify"
],
"health": {
"kind": "unit"
}
}
],
"build": {