I tried to redirect the output of the time command, but I couldn\'t:
$time ls > filename
real 0m0.000s
user 0m0.000s
sys 0m0.000s
The command time sends it's output to STDERR (instead of STDOUT). That's because the command executed with time normally (in this case ls) outputs to STDOUT.
If you want to capture the output of time, then type:
(time ls) 2> filename
That captures only the output of time, but the output of ls goes normal to the console. If you want to capture both in one file, type:
(time ls) &> filename
2> redirects STDERR, &> redirects both.
no need to launch sub shell. Use a code block will do as well.
{ time ls; } 2> out.txt
or
{ time ls > /dev/null 2>&1 ; } 2> out.txt
time is shell builtin and I'm not sure if there is way to redirect it. However you can use
/usr/bin/time
instead, which definitely accept any output redirections.
I use the redirection of stdout and stderr method with braces for testing.
The &>>rpt
represents this >>rpt 2>&1
but shorter.
The braces will execute a command(s) in the current shell. See: man bash
{ time ls a*; } &>>rpt
The reason why redirection does not seem to work with time
is that it's a bash reserved word (not a builtin!) when used in front of a pipeline. bash(1):
If the time reserved word precedes a pipeline, the elapsed as well as user and system time consumed by its execution are reported when the pipeline terminates.
So, to redirect output of time
, either use curly braces:
{ time ls; } 2> filename
Or call /usr/bin/time
:
/usr/bin/time ls 2> filename
you can redirect the time output using,
(time ls) &> file
Because you need to take (time ls) as a single command so you can use braces.