summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/next-daemon.md10
1 files changed, 7 insertions, 3 deletions
diff --git a/docs/next-daemon.md b/docs/next-daemon.md
index f60e32ab..500b53fe 100644
--- a/docs/next-daemon.md
+++ b/docs/next-daemon.md
@@ -240,8 +240,11 @@ Decisions taken at the forks, with the ponytail lens:
session as before: in the terminal's own process, ended by its hangup,
for a harness that kills by pid and closes the terminal. A GUI test
window (`PARDES_TEST`) has none unless `PARDES_DAEMON=on`.
-- **Known gaps.** A stub killed with SIGKILL while its terminal stays open
- leaves the session drawing there until the terminal closes or Detach. A
+- **Known gaps.** A forked session takes its stub's death, a SIGKILL
+ too, as a HUP (PR_SET_PDEATHSIG; FreeBSD's PROC_PDEATHSIG_CTL) and
+ detaches; a `pardes --attach` stub is no parent of its session, and one
+ killed with SIGKILL while its terminal stays open still leaves the
+ session drawing there until the terminal closes or Detach. A
reattached terminal keeps the first one's environment (TERM, COLORTERM);
vaxis queries its capabilities again. A daemon killed outright leaves
its sessions unregistered, and Detach then refuses. A daemon of an older
@@ -378,7 +381,8 @@ Everything of ours lives in `/root/pardes-test`, nothing outside it.
- Off Linux, the parts of tests whose refusing path is Linux's
/proc/1 are skipped, and so is the builtins JSON check, since the
committed lists are Linux builds' (Tty9p included).
- - test/daemon.py passes there at 20 cycles. One earlier run failed at
+ - test/daemon.py passes there at 20 cycles, its killed stub included
+ (procctl's death signal). One earlier run failed at
cycle 3, one process short in its count (most likely ps -e failing to
read an environment).
- test/fs.py runs past its `pardes -` +Pager checks now, as far as the