diff options
author | Jim Meyering <meyering@redhat.com> | 2007-10-20 12:00:54 +0200 |
---|---|---|
committer | Jim Meyering <meyering@redhat.com> | 2007-10-20 12:00:54 +0200 |
commit | 4319cbc0a131a63c7f1adbc21c617e767d525b12 (patch) | |
tree | d201464303517985117a018344593b7e8bd31b52 /doc/coreutils.texi | |
parent | 5dabe472b07c1962783838ed83ec8fcd1faa4389 (diff) | |
download | coreutils-4319cbc0a131a63c7f1adbc21c617e767d525b12.tar.xz |
* doc/coreutils.texi (tee invocation): Fix typo. Add a little.
Diffstat (limited to 'doc/coreutils.texi')
-rw-r--r-- | doc/coreutils.texi | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 3aec8e58d..c729b2265 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -11056,7 +11056,7 @@ Ignore interrupt signals. @end table -The @command{tee} is useful when you happen to be transferring a large +The @command{tee} command is useful when you happen to be transferring a large amount of data and also want to summarize that data without reading it a second time. For example, when you are downloading a DVD image, you often want to verify its signature or checksum right away. @@ -11086,8 +11086,9 @@ checksum in a file named @file{dvd.sha1}. Note, however, that this example relies on a feature of modern shells called process substitution (the @samp{>(command)} syntax, above), -so you can use @command{zsh}, @command{bash}, or @command{ksh}, but -not a minimal @command{/bin/sh}. +so it works with e.g., @command{zsh}, @command{bash}, or @command{ksh}, +but not with a minimal @command{/bin/sh}. So if you use this technique +in a shell script, be sure to start the script with @samp{#!/bin/bash}. You can extend this example to make @command{tee} write to two processes, computing MD5 and SHA1 checksums in parallel: |