Rsync hangs in Snow Leopard

Post to the Unix forum under OS X Technologies.

Rsync is a bit outdated, probably be best to compile rsync 3.0.5.
http://www.bombich.com/mactips/rsync.html

Kj
If you have trouble compiling it let me know, I have it already compiled.

Here is a link to rsync 3.0.5 and rsync 3.0.6,
I have been using rsync 3.0.5 for some time now and it is stable (under10.5.7).
I just compiled (10 minutes ago) rsync 3.0.6 under Snow Leopard. You're welcome
to beta test it for me 😉

http://azlist.info/kj/mac/utilities/

Kj

Any luck with this? I can get my computers to lock up by doing:

rsync -av /Network/Drive1 /Network/Drive2

Its very frustrating because my backups no longer work.

USAGE
You use rsync in the same way you use rcp. You must specify a source
and a destination, one of which may be remote.

Perhaps the best way to explain the syntax is with some examples:

rsync -t *.c foo:src/

This would transfer all files matching the pattern *.c from the current
directory to the directory src on the machine foo. If any of the files
already exist on the remote system then the rsync remote-update proto-
col is used to update the file by sending only the differences. See the
tech report for details.

rsync -avz foo:src/bar /data/tmp

This would recursively transfer all files from the directory src/bar on
the machine foo into the /data/tmp/bar directory on the local machine.
The files are transferred in "archive" mode, which ensures that sym-
bolic links, devices, attributes, permissions, ownerships, etc. are
preserved in the transfer. Additionally, compression will be used to
reduce the size of data portions of the transfer.

rsync -avz foo:src/bar/ /data/tmp

A trailing slash on the source changes this behavior to avoid creating
an additional directory level at the destination. You can think of a
trailing / on a source as meaning "copy the contents of this directory"
as opposed to "copy the directory by name", but in both cases the
attributes of the containing directory are transferred to the contain-
ing directory on the destination. In other words, each of the follow-
ing commands copies the files in the same way, including their setting
of the attributes of /dest/foo:

rsync -av /src/foo /dest
rsync -av /src/foo/ /dest/foo

Note also that host and module references don't require a trailing
slash to copy the contents of the default directory. For example, both
of these copy the remote directory's contents into "/dest":

rsync -av host: /dest
rsync -av host::module /dest

You can also use rsync in local-only mode, where both the source and
destination don't have a `:' in the name. In this case it behaves like
an improved copy command.

Finally, you can list all the (listable) modules available from a par-
ticular rsync daemon by leaving off the module name:

rsync somehost.mydomain.com::

See the manual for more details.
man rsync

rsync hangs for me as well, and I even installed 3.0.6 from Macports.

I'm just doing it to an external hard disk, this command has worked for like forever before, but now hangs in the middle of doing its thing, for no apparent reason. I've checked disks with disk utility and nothing

rsync -avE --delete ~ /Volumes/Great\ Basin/Lusers || echo -n


Dave

I have been using rsync 3.0.5 with Snow Leopard. It seems to work OK.
I compiled 3.0.6, but I only tested it briefly.

Try the one from Rudix:
http://rudix.org/packages-rst.html

Kj

I downloaded and compiled Rsync 3.0.6 and have ran into several problems:

Compiling on PPC and running it on an intel fails to run properly in rosetta, (weird rsync errors) so I have to have multiple compiled images. Must run the intel build on the intel machines. And of course must run the PPC compiles on the PPCs.

Bigger problem though is that I can no longer make a bootable backup. I was able to use rsync to duplicate the 10.6.0 install image, but not an installation of Snow Leopard on a newer Mac Pro. The install KPs early during boot while trying to get launchd moving.

The command being used is:

sudo "/usr/local/bin/rsync 306intel" -aHAXx --delete -v --progress --numeric-ids --exclude=private/var/vm/* --exclude=.fseventsd/* "/Volumes/Snow Leopard MP GUID/" "/Volumes/Service Snow/"

The command completes with no errors or warnings, and when rerun it finds only a couple of the usual continuously updated dot files. But it will fast KP the same mac pro that booted the source drive moments ago.

I've also discovered that it's hard to make a bootable backup from the booted system or others that have been run. Sockets are (ONCE AGAIN) generating errors when all options are enabled for a full backup. They are the type of socket that get rebuilt as needed by the system, but there are dozens so its impractical to --exclude all of them. But if rsync sees them it causes an rsync io error, which cancels file deletion. (no way to override?) Sockets seem to be the bane of rsync, I was using 2.6.3 even when 2.6.9 was out because of resource fork and socket problems with rsync.

Do these forums always tag threads with "answered responses = 1"? There are a lot of threads here with NO answers that are so tagged at the top.

So does anyone know of a way to get rsync 3.0.6 to make a bootable backup of a (non live is fine) snow leopard installation?

So does anyone know of a way to get rsync 3.0.6 to make a bootable backup of a (non live is fine) snow leopard installation?

Yes. Download and run CCC 3.3 b5. See http://forums.bombich.com/viewtopic.php?t=14707 for details.

Some versions of rsync will hang under Snow Leopard (Mac OS 10.6). If you compile rsync from the source code you should find that this issue is resolved.

Compilation Instructions Link : http://connect.homeunix.com/lbackup/developer/overview