openclaw/docs
openclaw/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(sync): mirror docs from openclaw/openclaw@9289a502bb

Browse Source
This commit is contained in:
openclaw-docs-sync[bot] 2026-04-30 15:33:56 +00:00
parent 96d260cca0
commit a799566e2c
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.openclaw-sync/source.json
View File

@ -1,5 +1,5 @@
{
"repository": "openclaw/openclaw",
"sha": "de1ac12f1c04eebc010edb4db05a4ad0aab05300",
"syncedAt": "2026-04-30T15:12:55.708Z"
"sha": "9289a502bb070c51dd86e9b3f10538398e36da54",
"syncedAt": "2026-04-30T15:32:29.061Z"
}

2
docs/gateway/gateway-lock.md
View File

@ -28,7 +28,7 @@ title: "Gateway lock"
## Operational notes
- If the port is occupied by _another_ process, the error is the same; free the port or choose another with `openclaw gateway --port <port>`.
- Under a service supervisor, a new gateway process that sees an existing healthy `/healthz` responder exits successfully and leaves that process in control. If the existing process never becomes healthy, retries are bounded and startup fails with a clear lock error instead of looping forever.
- Under a service supervisor, a new gateway process that sees an existing healthy `/healthz` responder leaves that process in control. On systemd, the duplicate starter exits with code 78 so the default `RestartPreventExitStatus=78` stops `Restart=always` from looping on a lock or `EADDRINUSE` conflict. If the existing process never becomes healthy, retries are bounded and startup fails with a clear lock error instead of looping forever.
- The macOS app still maintains its own lightweight PID guard before spawning the gateway; the runtime lock is enforced by the lock file plus HTTP/WebSocket bind.
## Related