5 ms·

On macOS you can monitor the progress of many commands with Ctrl-T. With cp for example: $ cp Test Test2 ^T load: 3.42 cmd: cp 86526 running 0.01u

On macOS you can monitor the progress of many commands with Ctrl-T. With cp for example: $ cp Test Test2 ^T load: 3.42 cmd: cp 86526 running 0.01u 4.36s Test -> Test2 6%

ripa 8y ago
Courtesy of FreeBSD’s SIGIFO https://www.freebsd.org/cgi/man.cgi?query=siginfo&sektion=3&apropos=0&manpath=FreeBSD+9.2-RELEASE https://www.freebsd.org/cgi/man.cgi?query=siginfo&sektion=3&...
beezle 8y ago
Yes, but Ctrl T goes back to at least TOPS-20
- deleted 8y ago
  [deleted]
oh5nxo 8y ago
On FreeBSD, in addition to the ^T, procstat -af is often useful.
sjmulder 8y ago
SIGINFO is very useful. I make it a point to implement support for it whenever it makes sense. Wish Linux would get it.
- moviuro 8y ago
  Some GNU utils use USR1 instead. It's not ideal, but it gets the job done. I'd also like to map ^T to `kill -USR1 <pid>` on my machines, but didn't research it much. > Sending an ‘INFO’ signal (or ‘USR1’ signal where that is unavailable) to a running dd process makes it print I/O statistics to standard error and then resume copying. [0] [0] https://www.gnu.org/software/coreutils/manual/html_node/dd-invocation.html#dd-invocation https://www.gnu.org/software/coreutils/manual/html_node/dd-i...
deleted 8y ago
[deleted]