[BusyBox] ash exits if a child process exits with non-blocking stdin
Erik Andersen
andersen at codepoet.org
Thu Aug 19 18:22:30 UTC 2004
On Thu Aug 19, 2004 at 02:54:05PM +0400, Vladimir N. Oleynik wrote:
> Matt,
>
> >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
Thanks vodz. Applied.
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
More information about the busybox
mailing list