>> What's wrong with this? > > The wrong thing is that it waits for three seconds. > In this construct: > > producer | consumer > > when producer closes its stdout, consumer will see EOF > at once when it reads its stdin, even if producer > does not terminate. In > > consumer <<(producer) > > construct, this is not the case. Not because it is documented > to work that way, but only because of the implementation. > For example, alternate implementation with named pipes in > e.g. /tmp will not have this peculiarity (but will have other > problems). >
Hi, so far i know the thread started as : how can i circumvent the read | while subshell problem ? We found 3 to 5 solutions (something like that) and what problem exactly is solved now by added the <<() feature ? perhaps adding something like "advanced ASH scripting in Busybox" is a more easy extension that adding new features ? re, wh _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
