Hello, I have compiled v3.0.4 of rsync per http://www.bombich.com/mactips/rsync.html. Unfortunately, I can't get rsync v3.0.4 to work properly. If I execute this command on the target Mac, I receive this error. sudo rsync -An --progress --log-file=docs_transfer server.domain.com:/Volumes/File_Storage/docs /Volumes/File_Storage rsync: on remote machine: -vnpAe.Ls: unknown option rsync error: syntax or usage error (code 1) at /SourceCache/rsync/rsync-24/rsync/main.c(1099) rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at 90.c(632) [receiver=3.0.4] Now, I thought I would just execute the same command in the opposite direction (from source Mac), but I receive an error there as well. rsync: on remote machine: -vnpA3.s: unknown option rsync error: syntax or usage error (code 1) at /SourceCache/rsync/rsync-35.2/rsync/main.c(1333) [server=2.6.9] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] A Google search reveals this is (allegedly) related to one of the versions not matching, but executing rsync --version on both systems results in v3.0.4 being reported. Any ideas as to what might be going on here? Do I have to remove the Apple supplied rsync to get this working? Is there some way to force both Macs to use v3.0.4, even though they are reporting that as the loaded version? I see the second error indicates a Mac is using v2.6.9, even though it shouldn't be. Thanks for reading! -Jonathan
On Sat, 2008-11-08 at 00:44 -0500, Jonathan S. Abrams wrote:> I have compiled v3.0.4 of rsync per > http://www.bombich.com/mactips/rsync.html. Unfortunately, I can't get > rsync v3.0.4 to work properly. > > If I execute this command on the target Mac, I receive this error. > > sudo rsync -An --progress --log-file=docs_transfer > server.domain.com:/Volumes/File_Storage/docs /Volumes/File_Storage > > rsync: on remote machine: -vnpAe.Ls: unknown option > rsync error: syntax or usage error (code 1) at > /SourceCache/rsync/rsync-24/rsync/main.c(1099) > rsync: connection unexpectedly closed (0 bytes received so far) [receiver] > rsync error: error in rsync protocol data stream (code 12) at 90.c(632) > [receiver=3.0.4] > > Now, I thought I would just execute the same command in the opposite > direction (from source Mac), but I receive an error there as well. > > rsync: on remote machine: -vnpA3.s: unknown option > rsync error: syntax or usage error (code 1) at > /SourceCache/rsync/rsync-35.2/rsync/main.c(1333) [server=2.6.9] > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(632) > [sender=3.0.4] > > A Google search reveals this is (allegedly) related to one of the > versions not matching, but executing rsync --version on both systems > results in v3.0.4 being reported. Any ideas as to what might be going > on here? Do I have to remove the Apple supplied rsync to get this > working? Is there some way to force both Macs to use v3.0.4, even > though they are reporting that as the loaded version? I see the second > error indicates a Mac is using v2.6.9, even though it shouldn't be.Probably commands executed over ssh (such as the remote rsync) get a different $PATH than your interactive session, and the old rsync is first in this $PATH. To fix that, specify the location of the rsync executable you want to use on the remote side using the --rsync-path option. This issue is similar to http://rsync.samba.org/FAQ.html#8 . Matt
I agree with Matt it looks like the old version is still in use. If you would like to run backups with rsync on Mac OS X, then you may be interested in LBackup. Once you have rsync working it is just a matter of dropping LBackup in place. Also, LBackup manages rsync paths from within a backup configuration file. Hope this helps.>> I have compiled v3.0.4 of rsync per >> http://www.bombich.com/mactips/rsync.html. Unfortunately, I can't get >> rsync v3.0.4 to work properly. >> >> If I execute this command on the target Mac, I receive this error. >> >> sudo rsync -An --progress --log-file=docs_transfer >> server.domain.com:/Volumes/File_Storage/docs /Volumes/File_Storage >> >> rsync: on remote machine: -vnpAe.Ls: unknown option >> rsync error: syntax or usage error (code 1) at >> /SourceCache/rsync/rsync-24/rsync/main.c(1099) >> rsync: connection unexpectedly closed (0 bytes received so far) >[receive r] >> rsync error: error in rsync protocol data stream (code 12) at 90.c(632) >> [receiver=3.0.4] >> >> Now, I thought I would just execute the same command in the opposite >> direction (from source Mac), but I receive an error there as well. >> >> rsync: on remote machine: -vnpA3.s: unknown option >> rsync error: syntax or usage error (code 1) at >> /SourceCache/rsync/rsync-35.2/rsync/main.c(1333) [server=2.6.9] >> rsync: connection unexpectedly closed (0 bytes received so far) [sender] >> rsync error: error in rsync protocol data stream (code 12) at io.c(632) >> [sender=3.0.4] >> >> A Google search reveals this is (allegedly) related to one of the >> versions not matching, but executing rsync --version on both systems >> results in v3.0.4 being reported. Any ideas as to what might be going >> on here? Do I have to remove the Apple supplied rsync to get this >> working? Is there some way to force both Macs to use v3.0.4, even >> though they are reporting that as the loaded version? I see the second >> error indicates a Mac is using v2.6.9, even though it shouldn't be. >
I was interested by this compilation on OSX 10.4. I followed the same Bombich instructions, and I thought I was successful, since I have found the following in the /usr/local/bin directory with today's date: -rwxr-xr-x 1 root staff 1011412 Nov 8 14:46 rsync Hovever when I perform the command rsync --version, I still find the old version: rsync version 2.6.9 protocol version 29 Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others. etc..... I though that adding the following in my ~/.profile file would help, but no change export PATH=$PATH:/usr/local/bin Any idea on how to solve this? I must admit I am a beginner .... Rgds
Thanks....
The strange thing is that the manual indicates that the command --
rsync-path=XXXX is related to the program to be run on the remote
machine. In my case there is no remote machine, since I experiment
with backing up on one local disk....
I used to use a relatively simple command in a back-up script such as:
for i in ${folderSourceToBackup}*
#some filtering code
rsync -aEv --delete --exclude=${exceptions} --delete-excluded ${i} "$
{backupTo}"
#etc
I still wonder wether migrating to the most recent version of Rsync
is useful in my case... It is educational anyhow.
Rgds
>The strange thing is that the manual indicates that the command -- >rsync-path=XXXX is related to the program to be run on the remote >machine. In my case there is no remote machine, since I experiment >with backing up on one local disk....As Jonathan pointed out, you may need to specify the local path ("/usr/local/bin") when calling rsync as well as using the rsync-path option ("rsync-path=XXXX") for specifying the remote rsync path. LBackup supports both of these path options within each backup configuration file. This is because a backup server may be backing up various operating systems which may have rsync installed in different locations.>I still wonder wether migrating to the most recent version of Rsync >is useful in my case... It is educational anyhow.This will depend upon how much meta-data you wish to preserve during a network file transfer. The most recent version of rsync will preserve a great deal of Mac OS X meta-data. If you are using rsync for backup, then your backup policy will assist you with decideing which backup tool to use. This desision should be influenced by the requirments of your backup policy. If you are running rsync on Mac OS X systems with HFS+ file systems and meta-data preservation is important to you, then I would reccomend upgrading to the latest version of rsync for network data transfers. Rsync 3.0.4 dose a good of handling a great deal of Mac OS X meta-data. Finally, A big thank you to everyone who is working on rsync. I have been very impressed with improved Mac OS X support. The 3.0.4 release and also the 3.0.3 release have featured major improvments for Mac OS X users. Your work is appretiated. Thank you! Hope this helps.