Hi,
I've observed some strange behavior in ash buildin "read" when
a SIGCHLD arrives in current busybox.
old behavior on busybox 1.24.2 ash (same behavior also on Debian bash and dash)
sleep 1& read x
=> waits for ever until input is given
new behavior on busybox
sleep 1& read x
[1]+ Done sleep 1
=> read will be interrupted after one second due raise of SIGCHLD
I am not sure what is the right place to fix this. Any comment on this?
For me it works to suppress this signal on the corresponding poll() call.
Best,
Guido
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
