tee (command)

The typical syntax on a Unix-based system can be described as:

tee [-a] [-i] [file...]

• file... One or more names for files to receive the command input data
• -a Append to a file rather than overwriting
• -i Ignore interrupts

Process substitution lets more than one process read the standard output of the originating process.[https://www.gnu.org/software/coreutils/manual/html_node/tee-invocation.html GNU Coreutils, tee invocation].

If a write to any file is not successful, writes to other files and standard output continue, but the exit status will indicate failure with a value greater than 0.

The following both displays the output of the lint program.c command and saves the output to a file named program.lint; overwriting it if it already existed.

lint program.c | tee program.lint

The following does the same as the previous example, except for appending the output to an existing file instead of overwriting it. The file is created if it was not pre-existing.

lint program.c | tee -a program.lint

The following bypasses a limitation of the sudo command which is unable to pipe standard output to a file. By dumping its stdout stream into /dev/null, output to the console suppressed. This gives the current user root access to a server over ssh, by installing the user's public key to the server's key authorization list.

cat ~/.ssh/id_rsa.pub | ssh admin@server "sudo tee -a /root/.ssh/authorized_keys2 > /dev/null"

In Bash, the output can be filtered before being written to the file—without affecting the output displayed—by using process substitution. The following removes common ANSI escape codes before writing to ls.txt, but retains them for display.{{cite web|title=GNU Coreutils: tee invocation|url=https://www.gnu.org/software/coreutils/manual/html_node/tee-invocation.html#index-_002d_002doutput_002derror|access-date=3 February 2016}}

ls --color=always | tee >(sed "s/\x1b[^m]*m//g" > ls.txt)

The syntax on 4DOS and 4NT can be described as:

TEE [/A] file...

• file One or more names for files to receive the command input data
• /A Append to a file rather than overwriting

When used with a pipe, the output of the previous command is written to a temporary file. When that command finishes, {{code|tee}} processes the temporary file; copying it to the file argument(s) and standard output.

This example searches the file wikipedia.txt for any lines containing the string "4DOS", makes a copy of the matching lines in 4DOS.txt, sorts the lines, and writes them to the output file 4DOSsorted.txt:

>find "4DOS" wikipedia.txt | tee 4DOS.txt | sort > 4DOSsorted.txt

Powershell is not suitable for binary and raw data, always treats the stream as text, and modifies the data as it is transferred.

The syntax on PowerShell can be described as:

tee [-FilePath] [-InputObject ]

tee -Variable [-InputObject ]

• -InputObject Specifies the object input to the cmdlet. The parameter accepts variables that contain the objects and commands or expression that return the objects.
• -FilePath Specifies the file where the cmdlet stores the object. The parameter accepts wildcard characters that resolve to a single file.
• -Variable A reference to the input objects will be assigned to the specified variable.

The command is implemented as a ReadOnly command alias that invokes the cmdlet named Microsoft.PowerShell.Utility\Tee-Object.

The following displays the standard output of command ipconfig in the console window, and simultaneously saves a copy of it in the file OutputFile.txt.

ipconfig | tee OutputFile.txt

The following shows that the piped input for tee can be filtered and that tee is used to display that output, which is filtered again so that only processes owning more than 1000 handles are displayed, and writes the unfiltered output to the file ABC.txt. To display and save all running processes, filtered so that only programs starting with svc and owning more than 1000 handles are output:

Get-Process | Where-Object { $_.Name -like "svc*" } | Tee-Object ABC.txt | Where-Object { $_.Handles -gt 1000 }

• {{Annotated link|GNU Core Utilities}}
• {{Annotated link|List of POSIX commands}}
• {{Annotated link|syslog}}

{{Reflist}}

• {{Cite book|author-last=McElhearn|author-first=Kirk|title=The Mac OS X Command Line: Unix Under the Hood|date=2006|publisher=John Wiley & Sons|isbn=978-0470113851}}

{{Wikibooks|Guide to Unix|Commands}}

• An introduction on Linux I/O Redirection [http://wadhavankar.org/tn/linux/user/standardIo.php "Linux I/O Redirection"] {{Webarchive|url=https://web.archive.org/web/20120610042438/http://wadhavankar.org/tn/linux/user/standardIo.php |date=10 June 2012 }} with tee
• [https://www.gnu.org/software/coreutils/manual/html_node/tee-invocation.html GNU tee manual]
• {{man|cu|tee|SUS|duplicate standard input}}
• {{man|1|tee|Plan 9}}
• {{man|1|tee|Inferno}}
• [https://github.com/tothpaul/Delphi-Tee Delphi-Tee] - Delphi (software) OpenSource implementation

{{Unix commands}}

{{Plan 9 commands}}

{{Core Utilities commands}}

{{Windows commands}}

{{Use dmy dates|date=March 2018}}

Category:Unix text processing utilities

Category:Unix SUS2008 utilities

Category:Plan 9 commands

Category:Inferno (operating system) commands

Category:ReactOS commands

Category:IBM i Qshell commands

Category:Windows administration

Category:Inter-process communication