Development record
.abcd/development/brief/04-surfaces/17-guard.md:1013-1014 says an allow does not see a pid list a kill reads through a file or from a `ps | grep` chain. `ps aux | grep make | xargs kill`, the awk and `kill $(...)` forms and `pgrep make > p; kill $(cat p)` all exit 1 under kill-by-search. commands/guard.md:992 states that a filtered ps listing is a search.
issueopenminoriss-2611040555239973
.abcd/development/brief/04-surfaces/17-guard.md:1013-1014 says an allow does not see a pid list a kill reads through a file or from a ps | grep chain. ps aux | grep make | xargs kill, the awk and kill $(...) forms and pgrep make > p; kill $(cat p) all exit 1 under kill-by-search. commands/guard.md:992 states that a filtered ps listing is a search.
Frontmatter
| id | iss-2611040555239973 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2611040555239973-abcd-development-brief-04-surfaces.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2611060810012471`17-guard.md:1038` lists a pid list a kill reads through a variable or a file, or from a `ps | grep` chain, as unseen. `iss-2611040555239973` and `iss-2611040555220611` record the forms that block as `kill-by-search`. They do not record what stays true: `kill $(cat pidfile)` and a bare `kill $p` still allow, so removing the clause outright would leave the chapter implying those are seen. `p=$(ps aux | grep foo); kill $p` also blocks.