From 4319cbc0a131a63c7f1adbc21c617e767d525b12 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 20 Oct 2007 12:00:54 +0200 Subject: [PATCH] * doc/coreutils.texi (tee invocation): Fix typo. Add a little. --- ChangeLog | 2 ++ doc/coreutils.texi | 7 ++++--- 2 files changed, 6 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index d025e231ee..85d2ed260e 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,7 @@ 2007-10-20 Jim Meyering + * doc/coreutils.texi (tee invocation): Fix typo. Add a little. + Adjust tests to pass, now that Test.pm ones use check.mk. * tests/check.mk (vc_exe_in_TESTS): Adjust regexp not to match the "TESTS = $x-tests" line in each Test.pm-derived Makefile.am file. diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 3aec8e58df..c729b2265b 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: -- 2.47.2