13 ms·
On BSD, unlike Linux, many utilities including dd(1) will dump a progress report when receiving SIGINFO. This was traditionally bound to ^T in shells, either by
by brynet 11y ago
On BSD, unlike Linux, many utilities including dd(1) will dump a progress report when receiving SIGINFO. This was traditionally bound to ^T in shells, either by default or using stty(1).
- justin_vanw 11y agoIt's SIGUSR1 on Linux, however there is no signal bound to ^T in Linux, nor is it apparently possible to bind new ones. `killall -USR1 dd` works like a charm, or for the impatient: watch killall -USR1 dd
- oxplot 11y agoThis example highlights a very useful alternative function of `watch`: to simply run a command on regular intervals without caring about the output.
- agnivade 11y agoYea, but its a pain to open another tab and run another command and switch back to this tab to see the progress. Why they didn't give a progress bar in the first place beats me.
- echochar 11y agoprogress(1) is a separate utility on BSD; one of my favorites. (Although it is also built in to BSD ftp.) I regularly use progress with dd, tar and other utilities. At least one BSD dd now has a "msgfmt" option that outputs parseable, printf-style format strings. Truthfully, I prefer it when these basic utilities are static except for fixing bugs. Using the new features in scripts means the scripts might lose some portability.
- crishoj 11y agoThere's also the pv(1) utility on Linux and OS X Homebrew: DESCRIPTION pv shows the progress of data through a pipeline by giving infor- mation such as time elapsed, percentage completed (with progress bar), current throughput rate, total data transferred, and ETA. To use it, insert it in a pipeline between two processes, with the appropriate options. Its standard input will be passed through to its standard output and progress will be shown on standard error. (edit: formatting)
- whalesalad 11y agoI use this often on OS X :)