aboutsummaryrefslogtreecommitdiff
path: root/procps/kill.c
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2004-08-19 18:22:13 +0000
committerEric Andersen <andersen@codepoet.org>2004-08-19 18:22:13 +0000
commitcb01bb1d6876edbcff428b75f110ba1b237e08d9 (patch)
tree4252286f7781b0b890634077bc59caac66b3ff4e /procps/kill.c
parent9ab4657c8908b923a2e4a1cae97e0471bb51809e (diff)
downloadbusybox-cb01bb1d6876edbcff428b75f110ba1b237e08d9.tar.gz
Patch from Vladimir N. Oleynik:
On Wed Aug 18, 2004 at 06:52:57PM +0800, Matt Johnston wrote: > I've come across some strange-seeming behaviour when running programs > under Busybox (1.0.0-rc3) ash. If the child process sets stdin to be > non-blocking and then exits, the parent ash will also exit. A quick strace > shows that a subsequent read() from stdin returns EAGAIN (as would be > expected): Thanks! Patch attached. --w vodz
Diffstat (limited to 'procps/kill.c')
0 files changed, 0 insertions, 0 deletions