fix(supervision): reap owned session workers after monitor crash
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
d7397ed6cf
commit
e9b70b00b6
7 files changed
+206
-10
No files matched your search
@@ -59,9 +59,12 @@ stop gets 30 seconds then forced kill after five more, and each Shadowsocks join
|
||||
gets five seconds. Exceeding a join bound fails closed. Compose grants 240
|
||||
seconds. Reconcile after joining the monitor and before even stopping zapret:
|
||||
stop also sources config, so unknown state is never sourced. The sequential
|
||||
cleanup budget is 140 seconds; 240 seconds also covers an in-flight startup
|
||||
cleanup budget is 146 seconds; 240 seconds also covers an in-flight startup
|
||||
command and scheduling grace. Watchdogs run in fresh shell interpreters and
|
||||
cancel/join their own sleepers, including during PID 1's EXIT trap.
|
||||
The monitor has a verified private session. After a crash, remaining check/NFQ
|
||||
workers in that session are terminated and verified gone before reconciliation
|
||||
or reactivation; Shadowsocks, watchdogs and unrelated exec peers are excluded.
|
||||
|
||||
## Isolation and runtime contract
|
||||
|
||||
|
||||
Reference in new issue
Block a user