From: Jim Meyering <jim@meyering.net>
Date: Mon, 28 Jul 2003 10:15:11 +0000 (+0000)
Subject: (dd invocation): Explain that a SIGUSR1 signal
X-Git-Tag: v5.0.90~11
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9943b0564a5f964af8a55c341599ef981991aa72;p=thirdparty%2Fcoreutils.git

(dd invocation): Explain that a SIGUSR1 signal
makes dd give a progress report to stderr.
---

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 05dcd668b2..347ceb4924 100644
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -6231,6 +6231,24 @@ tape=/dev/rmt/0
 (dd bs=4k seek=1 count=0 && dd bs=512k) <$tape >$disk
 @end example
 
+Note that sending a @samp{SIGUSR1} signal to a running @command{dd}
+process makes it print to standard error the number of records read
+and written so far, then to resume copying.  In the example below,
+@command{dd} is run in the background to copy 10 million blocks.
+The @command{kill} command makes it output the first pair of
+intermediate record counts,
+and when @command{dd} completes, it outputs the final pair.
+
+@example
+$ dd if=/dev/zero of=/dev/null count 10M & pid=$!
+$ kill -USR1 $pid; sleep 99
+5403604+0 records in
+5403604+0 records out
+10485760+0 records in
+10485760+0 records out
+@end example
+
+
 @table @samp
 
 @item if=@var{file}