Xfennec / progress

Linux tool to show progress for cp, mv, dd, ... (formerly known as cv)

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Not showing cp (macOS)

mcandre opened this issue · comments

progress shows rsync but not cp.

Homebrew, macOS Catalina.

Have you installed coreutils package from brew ?
If you installed it, all commands are prefixed with g (for gnu), gcp, gls etc etc and an alias is created to "cp".
But even if you launch with cp in your shell, the binary name is gcp and progress don't monitor gcp command.

$ command -V cp
cp is /bin/cp

$ greadlink -f /bin/cp
/bin/cp

$ brew info coreutils
coreutils: stable 8.32 (bottled), HEAD
GNU File, Shell, and Text utilities
https://www.gnu.org/software/coreutils
Conflicts with:
  aardvark_shell_utils (because both install `realpath` binaries)
  b2sum (because both install `b2sum` binaries)
  ganglia (because both install `gstat` binaries)
  gegl (because both install `gcut` binaries)
  idutils (because both install `gid` and `gid.1`)
  md5sha1sum (because both install `md5sum` and `sha1sum` binaries)
  truncate (because both install `truncate` binaries)
  uutils-coreutils (because coreutils and uutils-coreutils install the same binaries)
/usr/local/Cellar/coreutils/8.32 (476 files, 9.2MB) *
  Poured from bottle on 2020-05-05 at 17:57:29
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/coreutils.rb
License: GPL-3.0-or-later
==> Options
--HEAD
	Install HEAD version
==> Caveats
Commands also provided by macOS have been installed with the prefix "g".
If you need to use these commands with their normal names, you
can add a "gnubin" directory to your PATH from your bashrc like:
  PATH="/usr/local/opt/coreutils/libexec/gnubin:$PATH"
==> Analytics
install: 44,027 (30 days), 129,623 (90 days), 605,062 (365 days)
install-on-request: 40,449 (30 days), 118,557 (90 days), 539,140 (365 days)
build-error: 0 (30 days)

Update:

cp is now showing up on macOS progress.

I think my machine is just really slow and confused at the moment. For example, I have leftover cp test commands that even kill -9 are not able to terminate. Hopefully rebooting helps macOS get back to a good state.