However, perhaps reblock's more common purpose now, is for getting a running tally of transfer throughput, like in these two examples. The first shows using reblock where filesize is available via fstat, and the second shows reblock usage where filesize info is not available via fstat.
[root@blee bin]# reblock 65536 30 < /tmp/vnc-ltsp.tar.gz | ssh firstname.lastname@example.org 'cat > /tmp/vnc-ltsp.tar.gz' stdin seekable, and file len nonzero - will give percentage. File length is 212106 Kilobytes email@example.com's password: 1.0% 29s 35m 1h Kbytes: 2240.0 Kbits/s: 293.0 Gbytes/hr: 0.1 min: 1.0 2.1% 9s 34m 1h Kbytes: 4480.0 Kbits/s: 294.0 Gbytes/hr: 0.1 min: 2.0 3.1% 48s 32m 1h Kbytes: 6656.0 Kbits/s: 295.1 Gbytes/hr: 0.1 min: 3.0 3.8% 56s 31m 1h Kbytes: 8192.0 Kbits/s: 295.7 Gbytes/hr: 0.1 min: 3.6
tesuji-strombrg> du -sk palm-compilers 157632 palm-compilers Thu Jan 06 11:44:47 tesuji-strombrg> (cd palm-compilers && tar cf - .) | reblock -e 157632 -t 65536 30 | ssh nsc-1.nacs.uci.edu 'cat > /tmp/cmps.backup.tar' stdin not seekable - will not give percentage Estimated filetransfer size is 161415168 bytes Estimated percentages will only be as accurate as your size estimate /usr/X11R6/bin/xauth: error in locking authority file /Dcs/staff/strombrg/.Xauthority.0 (estimate: 48.6% 3s 1m) Kbytes: 76672.0 megabits/s: 9.9 gigabytes/hr: 4.3 min: 1.0 (estimate: 97.8% 2s) Kbytes: 154240.0 megabits/s: 11.7 gigabytes/hr: 5.1 min: 1.7 Thu Jan 06 11:46:56 tesuji-strombrg>
Please note that you only need to provide an estimate of the transfer
size if both of the following are true:
Usage is like:
usage: /usr/local/bin/reblock [-nt] [-t] [-e n] [-g /fs] [-S size] blocksize timeout -s n sleep n (fractions of) seconds between blocks -S size transfer no more than "size" bytes -b beep three times when transfer completes on stderr -t reports throughput (default now) -nt does not report throughput -e n says we're estimating that the filesize is n kilobytes -g /fs guess the number of Kilobytes in /fs. Can be repeated. -m metacompress mode :) -M metacompress mode with disk-based compression(s) :) (not implemented yet!) -f give a final report only, not a running report -np do not pad the final block to a full length block blocksize in bytes timeout in seconds (floating point)
reblock just writes a bunch of data followed by a carriage return, to give a running tally of how things are going. It will often write more than 80 characters on a line though, so if you see reblock scrolling really fast, you probably need to resize your terminal emulator (xterm, rxvt, gnome-terminal, konsole, &c) to be wide enough to hold the entire line.
You can download it here.
And you can get here
You can e-mail the author with questions or comments: