.\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH pee 1 2016-12-20 moreutils moreutils
.SH NAME
pee \- tee standard input to pipes
.SH SYNOPSIS
'nh
.fi
.ad l
\fBpee\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
[--[no-]ignore-sigpipe] [--[no-]ignore-write-errors] [\fI"command"\fR\&...]
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
\fBpee\fR is like \fBtee\fR
but for pipes. Each command is run and fed a copy of the
standard input. The output of all commands is sent to
stdout.
.PP
Note that while this is similar to
\fBtee\fR, a copy of the input is not sent
to stdout, like tee does. If that is desired, use 
\fBpee cat ...\fR
.SH OPTIONS
.TP 
\*(T<\fB\-\-ignore\-sigpipe\fR\*(T>, \*(T<\fB\-\-no\-ignore\-sigpipe\fR\*(T>
Do (not) ignore SIGPIPE. Any command started
by \fBpee\fR might cause a SIGPIPE
when it exists. If you ignore SIGPIPE, you
probably also want to ignore write errors (see
below). Ignoring SIGPIPE is the default
behaviour.
.TP 
\*(T<\fB\-\-ignore\-write\-errors\fR\*(T>, \*(T<\fB\-\-no\-ignore\-write\-errors\fR\*(T>
Do (not) ignore write errors. When a command
started by \fBpee\fR is no more
accepting data via the pipe between itself and
\fBpee\fR, a write error occurs in
\fBpee\fR. If this error is not
ignored, \fBpee\fR is going to
terminate all child processes and exists. Ignoring
write errors is the default behaviour.
.SH "SEE ALSO"
\fBtee\fR(1),
\fBpipe\fR(7)
.SH AUTHOR
Miek Gieben