On Wed, Oct 28, 2015 at 02:15:15PM +0000, Thorsten Glaser wrote: Hello,
> > ?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? Maybe I'm wrong, but I think the problem pointed here is the time mksh takes to complete the task. The cause is probably that, whereas bash and dash, mksh has no built-in 'printf' per default, so each 'printf' occurence is ran from the PATH. ++ Seb.
