--ignore-sigpipe, --no-ignore-sigpipe
Do (not) ignore SIGPIPE. Any command started by pee 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.
--ignore-write-errors, --no-ignore-write-errors
Do (not) ignore write errors. When a command started by pee is no more accepting data via the pipe
between itself and pee, a write error occurs in pee. If this error is not ignored, pee is going to
terminate all child processes and exists. Ignoring write errors is the default behaviour.