Thorsten Glaser <[email protected]> wrote: |Steffen Nurpmeso dixit: |>and when running it it seems that mksh(1) (this is @(#)MIRBSD KSH |>R51 2015/07/10 packaged for ArchLinux) uses a (i'm guessing its |>edit) line buffer until that overflows the first time, before |>passing the final data through to STDOUT: | |Excuse me, I do not understand that paragraph. | |> ?0[sdaoden@wales tmp]$ time bash t.sh >/dev/null |> 0m0.05s real 0m0.03s user 0m0.01s system |> ?0[sdaoden@wales tmp]$ time dash t.sh >/dev/null |> 0m0.02s real 0m0.01s user 0m0.01s system |> ?0[sdaoden@wales tmp]$ time mksh t.sh >/dev/null |> 0m6.76s real 0m2.04s user 0m4.28s system | |There seems to be no data not sent to stdout?
I was surprised problem shows up even then, seemed to be a nice short way to give a glance at the problem in six lines, .. and made me think line-editor handling is in the way, somehow. Dunno if it's true. Output of script snippet you removed looked like that, too. Ciao, --steffen
