progress(1) - Linux man page
Name
progress - feed input to a command, displaying a progress bar
Synopsis
progress [-z] [-f file] [-l length] [-p prefix] cmd [args ...]
-
Description
The progress utility opens a pipe to cmd and feeds an input stream into it, while displaying a progress bar to standard output. If no filename is specified, progress reads from standard input. Where feasible, progress fstat(2)s the input to determine the length, so a time estimate can be calculated.
If no length is specified or determined, progress simply displays a count of the data and the data rate.
The options are as follows:
-f file' Read from the specified file instead of standardinput.
- -l length' Use the specified length for the time estimate, rather than attempting to fstat(2) the input. An optional suffix (per
strsuftoll(3)) may be given.
-p prefix' Print the given ''prefix'' text before (left of) the progress bar.
-z' Filter the input through gunzip(1). If -f is specified, calculate the length using gzip -l.
Exit Status
progress exits 0 on success.
Examples
The command
- progress -zf file.tar.gz tar xf -
will extract the file.tar.gz displaying the progress bar as time passes:
0% | | 0 0.00 KB/s --:-- ETA 40% |********** | 273 KB 271.95 KB/s 00:01 ETA 81% |************************* | 553 KB 274.61 KB/s 00:00 ETA 100% |*********************************| 680 KB 264.59 KB/s 00:00 ETAIf it is preferred to monitor the progress of the decompression process (unlikely), then
- progress -f file.tar.gz tar zxf -
could be used.
The command
- dd if=/dev/rwd0d ibs=64k | \
- progress -l 120g dd of=/dev/rwd1d obs=64k
will copy the 120 GB disk wd0 (/dev/rwd0d) to wd1 (/dev/rwd1d), displaying a progress bar during the operation.
See Also
ftp(1), strsuftoll(3)
History
progress first appeared in NetBSD 1.6.1. The dynamic progress bar display code is part of ftp(1).
Authors
progress was written by John Hawkinson <jhawk@NetBSD.org>. ftp(1)'s dynamic progress bar was written by Luke Mewburn.
Bugs
Since the progress bar is displayed asynchronously, it may be difficult to read some error messages, both those produced by the pipeline, as well as those produced by progress itself.
BSD April 3, 2004 BSD