Codex processes reverted to stdin wait state despite redirection fix
Source type:
obs· Harvested: 2026-05-04 · Original date: 2026-05-03T17:33:12.144Z Metadata:{"project":"lunhsiangyuan","type":"discovery","obs_id":65210}
obs/65210 · discovery · 2026-05-03T17:33:12.144Z
Codex processes reverted to stdin wait state despite redirection fix
檢查 codex log 發現所有 4 個 topic 又回到 “Reading additional input from stdin…” 狀態，且進程數又是 10 個（正常應該 4 個）。這與之前觀察到的 3 個成功寫入的 narrative 檔案矛盾。可能原因：(1) log 檔案是舊的，沒被新執行覆蓋；(2) < /dev/null 重定向沒有正確傳遞到 04-synthesize-codex.sh 內部的 codex exec 調用；(3) 進程在寫檔後又 hang 住了。這顯示 stdin blocking 問題比預期更頑固，需要在 04-synthesize-codex.sh 腳本內部直接修改 codex exec 調用方式。
Concepts: [“problem-solution”,“gotcha”,“what-changed”]
Facts: [“All 4 codex synthesis logs (/tmp/codex-v4-*.log) show “Reading additional input from stdin…” state again”,“Process count returned to 10 codex exec processes instead of expected 4”,“Previous check showed 3 narrative files successfully written (5525, 5179, 5219 bytes)”,“Contradiction between successful file writes and log state suggests log files may be stale or processes respawned”,“stdin redirection with < /dev/null appears ineffective or not properly propagated to codex exec command”]
[← 回 Alfred Brain Hub]