Issues installing rsync 3.0.9 - Mountain Lion

I personaly would like to update Rsync because of the security vulnerability in rsync before version 3.0.0pre6.

http://www.fortiguard.com/encyclopedia/vulnerability/#id=21153

But it doesn't seem worth it if updates keep reinstalling it (So much for security updates).

I was able to overcome this problem by editing the file at

/private/etc/paths

and putting

/usr/local/bin

ahead of

/usr/bin

Then reboot.

And for the man pages:

export MANPATH=/usr/local/share/man:/usr/share/man

Update: Mavericks

Homebrew fixes a lot of the problems for me with OSX having outdated/broken tools. On Mavericks I had to

brew install homebrew/dupes/rsync

mv /usr/bin/rsync /usr/bin/rsync.old

ln -s /usr/local/bin/rsync /usr/bin/rsync (symlink the new homebrew version)

in order for everything to play nice.

For me this fixed the issue of rsync hanging while transferring. The old rsync (2.6.9 and 3.0.9) would consistently (as in always) hang at arbitrary points during transfers.

The homebrew version also fixed errors of various and sundry types (permissions or file not found) while transferring metadata.

Hi there,

Sorry to tack this onto a relatively old thread, but /usr/bin now seems to be "locked" in El Capitan. What gives? Even with elevating permissions to root with sudo, I can't overwrite rsync 2.6.9 with the latest version I compiled.

If I try from Terminal, I get this:

MacBook-Pro:rsync-3.1.1 sethgoldin$ sudo mv /usr/local/bin/rsync /usr/bin

override rwxr-xr-x root/wheel for /usr/bin/rsync? (y/n [n]) y

mv: rename /usr/local/bin/rsync to /usr/bin/rsync: Operation not permitted

If I try in the GUI, I get this crazy dialogue box:

In El Capitan, do I now have to enable the root account, log into there, and take care of it from the root account?

Seth Goldin

Washington, DC

Figured out that in El Capitan, you'll need to temporarily disable System Integrity Protection: http://osxdaily.com/2015/10/05/disable-rootless-system-integrity-protection-mac- os-x/

That is NOT a good idea. Because OS X may do an update and remove your rsync update.

Better to put your rsync in /usr/local/bin (assuming SIP does not prevent putting your stuff in /usr/local/..., or /opt/local, or your own new customer tree. Then put the directory in your PATH. This is the standard Unix approach to adding your own versions of standard software so that you do not screw up system utilities and scripts that expects the original installed behavior, or have an OS update replace your version because it is where the OS expects to have its version.

Thanks. I didn't realize this. I actually called Apple Enterprise support, and they didn't know to do this. Instead, strangely, they suggested that I figure out, from non-Apple documentation online, how to temporarily disable SIP, instead of just throwing the software safely into /usr/local/bin. Will know going forward, though. Thanks!

Seth Goldin wrote:

Thanks. I didn't realize this. I actually called Apple Enterprise support, and they didn't know to do this. Instead, strangely, they suggested that I figure out, from non-Apple documentation online, how to temporarily disable SIP, instead of just throwing the software safely into /usr/local/bin. Will know going forward, though. Thanks!

They most likely have not been a Unix software developer for the past 20 years 🙂, nor have they lived with at least 8 different Unix flavors.

If you compiled rsync from source, then you can install in /usr/local/bin with sudo make install (this will also install the man pages in usr/local/man)

You can use an alias in .bash_profile: alias rsync='/usr/local/bin/rsync'

and also to search /usr/local first for man pages, so that newer man page for rsync is displayed:

export MANPATH=/usr/local/share/man:/usr/share/man