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:
@@ -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": {
|
||||
|
||||
Reference in New Issue
Block a user