How to redirect output to a file and stdout

LinuxBashFile IoIoStdout

Linux Problem Overview

In bash, calling foo would display any output from that command on the stdout.

Calling foo > output would redirect any output from that command to the file specified (in this case 'output').

Is there a way to redirect output to a file and have it display on stdout?

Linux Solutions

Solution 1 - Linux

The command you want is named tee:

foo | tee output.file

For example, if you only care about stdout:

ls -a | tee output.file

If you want to include stderr, do:

program [arguments...] 2>&1 | tee outfile

2>&1 redirects channel 2 (stderr/standard error) into channel 1 (stdout/standard output), such that both is written as stdout. It is also directed to the given output file as of the tee command.

Furthermore, if you want to append to the log file, use tee -a as:

program [arguments...] 2>&1 | tee -a outfile

Solution 2 - Linux

$ program [arguments...] 2>&1 | tee outfile

2>&1 dumps the stderr and stdout streams. tee outfile takes the stream it gets and writes it to the screen and to the file "outfile".

This is probably what most people are looking for. The likely situation is some program or script is working hard for a long time and producing a lot of output. The user wants to check it periodically for progress, but also wants the output written to a file.

The problem (especially when mixing stdout and stderr streams) is that there is reliance on the streams being flushed by the program. If, for example, all the writes to stdout are not flushed, but all the writes to stderr are flushed, then they'll end up out of chronological order in the output file and on the screen.

It's also bad if the program only outputs 1 or 2 lines every few minutes to report progress. In such a case, if the output was not flushed by the program, the user wouldn't even see any output on the screen for hours, because none of it would get pushed through the pipe for hours.

Update: The program unbuffer, part of the expect package, will solve the buffering problem. This will cause stdout and stderr to write to the screen and file immediately and keep them in sync when being combined and redirected to tee. E.g.:

$ unbuffer program [arguments...] 2>&1 | tee outfile

Solution 3 - Linux

Another way that works for me is,

<command> |& tee  <outputFile>

as shown in gnu bash manual


ls |& tee files.txt

> If ‘|&’ is used, command1’s standard error, in addition to its standard output, is connected to command2’s standard input through the pipe; it is shorthand for 2>&1 |. This implicit redirection of the standard error to the standard output is performed after any redirections specified by the command.

For more information, refer redirection

Solution 4 - Linux

You can primarily use Zoredache solution, but If you don't want to overwrite the output file you should write tee with -a option as follow :

ls -lR / | tee -a output.file

Solution 5 - Linux

Something to add ...

The package unbuffer has support issues with some packages under fedora and redhat unix releases.

Setting aside the troubles

Following worked for me

bash 2>&1 | tee output.log

> Thank you ScDF & matthew your inputs saved me lot of time..

Solution 6 - Linux

Using tail -f output should work.

Solution 7 - Linux

You can do that for your entire script by using something like that at the beginning of your script :

#!/usr/bin/env bash

test x$1 = x$'\x00' && shift || { set -o pipefail ; ( exec 2>&1 ; $0 $'\x00' "$@" ) | tee mylogfile ; exit $? ; }

# do whaetever you want

This redirect both stderr and stdout outputs to the file called mylogfile and let everything goes to stdout at the same time.

It is used some stupid tricks :

  • use exec without command to setup redirections,
  • use tee to duplicates outputs,
  • restart the script with the wanted redirections,
  • use a special first parameter (a simple NUL character specified by the $'string' special bash notation) to specify that the script is restarted (no equivalent parameter may be used by your original work),
  • try to preserve the original exit status when restarting the script using the pipefail option.

Ugly but useful for me in certain situations.

Solution 8 - Linux

Bonus answer since this use-case brought me here:

In the case where you need to do this as some other user

echo "some output" | sudo -u some_user tee /some/path/some_file

Note that the echo will happen as you and the file write will happen as "some_user" what will NOT work is if you were to run the echo as "some_user" and redirect the output with >> "some_file" because the file redirect will happen as you.

Hint: tee also supports append with the -a flag, if you need to replace a line in a file as another user you could execute sed as the desired user.

Solution 9 - Linux

< command > |& tee filename # this will create a file "filename" with command status as a content, If a file already exists it will remove existed content and writes the command status.

< command > | tee >> filename # this will append status to the file but it doesn't print the command status on standard_output (screen).

I want to print something by using "echo" on screen and append that echoed data to a file

echo "hi there, Have to print this on screen and append to a file" 

Solution 10 - Linux

In my case I had the Java process with output logs. The simplest solution to display output logs and redirect them into the file(named logfile here) was: |& tee logfile

> Result was Java process running with output logs displaying and > putting them into the file with name logfile

Solution 11 - Linux

tee is perfect for this, but this will also do the job

ls -lr / > output | cat output


All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionSCdFView Question on Stackoverflow
Solution 1 - LinuxZoredacheView Answer on Stackoverflow
Solution 2 - LinuxMatthew AlpertView Answer on Stackoverflow
Solution 3 - LinuxtsenapathyView Answer on Stackoverflow
Solution 4 - LinuxO.BadrView Answer on Stackoverflow
Solution 5 - Linuxnitinr708View Answer on Stackoverflow
Solution 6 - LinuxChuck PhillipsView Answer on Stackoverflow
Solution 7 - LinuxBruno BEAUFILSView Answer on Stackoverflow
Solution 8 - LinuxjorfusView Answer on Stackoverflow
Solution 9 - Linuxkiran saiView Answer on Stackoverflow
Solution 10 - LinuxJackkobecView Answer on Stackoverflow
Solution 11 - LinuxkalView Answer on Stackoverflow