diff options
| author | andersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2004-08-19 18:22:13 +0000 |
|---|---|---|
| committer | andersen <andersen@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2004-08-19 18:22:13 +0000 |
| commit | 50bff764c32353a67c2000c5d440c904959a9ec2 (patch) | |
| tree | 4252286f7781b0b890634077bc59caac66b3ff4e /init | |
| parent | 2c65f6410b9eeb88b7de651aa1aabfb57ce2af9e (diff) | |
| download | busybox-w32-50bff764c32353a67c2000c5d440c904959a9ec2.tar.gz busybox-w32-50bff764c32353a67c2000c5d440c904959a9ec2.tar.bz2 busybox-w32-50bff764c32353a67c2000c5d440c904959a9ec2.zip | |
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
git-svn-id: svn://busybox.net/trunk/busybox@9127 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions