sneak/routewatch
1
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

Let the daemon receive docker stop's signal itself (closes #33) #35

Merged
clawbot merged 2 commits from issue-33-stop-signal into next 2026-09-28 21:08:33 +02:00
Conversation 3 Commits 2 Files Changed 3
+2 -1
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit 3310376e2a - Show all commits
TODO.md
+2 -1
View File
@@ -26,7 +26,8 @@ runs make check on main.
- 2026-09-28: `docker stop` no longer kills the daemon 2 seconds after the - 2026-09-28: `docker stop` no longer kills the daemon 2 seconds after the
stop signal: the entrypoint switches to the `routewatch` user with stop signal: the entrypoint switches to the `routewatch` user with
`setpriv` instead of `runuser`, so the daemon receives the signal itself `setpriv` instead of `runuser`, so the daemon receives the signal itself
and gets its full 60 seconds to shut down (closes #33) and gets the whole wait `docker stop` allows, up to its own 60-second
limit (closes #33)
- 2026-09-28: ready to run under upaas: a set but invalid `PORT`, - 2026-09-28: ready to run under upaas: a set but invalid `PORT`,
`XDG_DATA_HOME` or `MALLOC_ARENA_MAX` stops the start, the health `XDG_DATA_HOME` or `MALLOC_ARENA_MAX` stops the start, the health
check follows `PORT`, README "Running under upaas" section (closes check follows `PORT`, README "Running under upaas" section (closes