search for: rsync3

Did anyone ever get rsync3 to compile as a universal binary and work correctly on both tiger and leopard on ppc and intel? David.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've compiled rsync 3.0.3 on OSX 10.4 PPC via the plain jane ./configure; make method (no patches). The resulting binary has then been moved to /usr/local/bin/rsync3 and copied to a OSX 10.5.4 Intel client machine as rsync3. I then run the following command: rsync3 -vvv -e ssh -avAX --progress --delete - --rsync-path='/usr/local/bin/rsync3' root@xserver:/Users/portman/Sites/index.html /Volumes/MacHardDisk/Users/portman/Sites/index.html Which results...

for those who care, the yodl pkg, a prereq for building rsync3-cvs docs (& more?), had 'issues' @ version <= v2.04 with building cleanly on osx. it's been updated today to v2.10, http://sourceforge.net/project/showfiles.php?group_id=126615 v2.10 builds clealy, without req'd patching or error, and works just fine when/as used by rsy...

...if (ret == -1) ! exit_cleanup(RERR_STARTCLIENT); else ! exit_cleanup(ret); ! return ret; } --- 880,889 ---- ret = start_client(argc, argv); if (ret == -1) ! exit_cleanup(RERR_STARTCLIENT); else ! exit_cleanup(ret); ! ! exit(ret); ! /* NOTREACHED */ } Index: rsync3.txt =================================================================== RCS file: /cvsroot/rsync/rsync3.txt,v retrieving revision 1.3 diff -c -r1.3 rsync3.txt *** rsync3.txt 12 Sep 2001 14:35:39 -0000 1.3 --- rsync3.txt 18 Feb 2002 00:39:34 -0000 *************** *** 192,199 **** Scripting issu...

From: Andrea Gelmini <andrea.gelmini at gelma.net> --- rsync3.txt | 22 +++++++++++----------- 1 files changed, 11 insertions(+), 11 deletions(-) diff --git a/rsync3.txt b/rsync3.txt index 42d77dc..293680f 100644 --- a/rsync3.txt +++ b/rsync3.txt @@ -1,6 +1,6 @@ -*- indented-text -*- -Notes towards a new version of rsync +Notes towards a new version of...

...a few minutes, even with a very large number of files (some users have up to ), the sync is done if there are not too many changed files. But when there are 3 or more rsync at the same time, all rsync become very very slow and can take a few hours to complete. Here are my options : /usr/local/bin/rsync3 --rsync-path=/usr/local/bin/rsync3 -aHXxvE --stats --numeric-ids --delete-excluded --delete-before --human-readable —rsh="ssh -T -c aes128-ctr -o Compression=no -x" -z --skip-compress=gz/bz2/jpg/jpeg/ogg/mp3/mp4/mov/avi/vmdk/vmem --inplace --chmod=u+w --timeout=60 —exclude=‘Caches' —e...

...2.6.1 gives, is what 2.6.2 is doing a valid bug? If so I'll go through the diff between the release and send a patch back. I have a pretty simple test case to reproduce at this point: (in rsync-2.6.1 source directory) $ ./configure $ make $ sudo ./rsync --daemon --no-detach & $ ./rsync rsync3.txt rsync://localhost/root mkstemp "/.rsync3.txt.LVaWT1" (in root) failed: Permission denied rsync error: some files could not be transferred (code 23) at main.c(633) $ echo $? 23 (in rsync-2.6.0 source directory) $ ./configure $ make $ sudo ./rsync --daemon --no-detach & $ ./rsync...

...system inums, 64-bit internal inums per Bombich instructions: > Capabilities: > 64-bit files, 32-bit inums, 64-bit timestamps, 64-bit long ints, > socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, > append, ACLs, xattrs, no iconv, symtimes, file-flags > file rsync3 > rsync3: Mach-O universal binary with 3 architectures > rsync3 (for architecture ppc): Mach-O executable ppc > rsync3 (for architecture i386): Mach-O executable i386 > rsync3 (for architecture x86_64): Mach-O 64-bit executable x86_64 Regards, Bryan > On 13 Dec 2014, at 4:04...

what is the source and destination filesystem? here is some report that rsync has some problem with HFS+ filesystems and "ressource forks": http://quesera.com/reynhout/misc/rsync+hfsmode/ but as you are using ubuntu and not osx i`m curious what`s the problem, so i think we need more information here. regards roland > Gesendet: Freitag, 12. Dezember 2014 um 15:31 Uhr > Von:

...> > per Bombich instructions: >> Capabilities: >> 64-bit files, 32-bit inums, 64-bit timestamps, 64-bit long ints, >> socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, >> append, ACLs, xattrs, no iconv, symtimes, file-flags > >> file rsync3 >> rsync3: Mach-O universal binary with 3 architectures >> rsync3 (for architecture ppc): Mach-O executable ppc >> rsync3 (for architecture i386): Mach-O executable i386 >> rsync3 (for architecture x86_64): Mach-O 64-bit executable x86_64 > > > > Regards, &gt...

An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20141214/3d32f770/attachment.html>

hi, as it's been awhile since my last attempts w/ v269, i'm building the latest rsync3-svs on osx 10.4.8; looking to see what's evolved re: acls & xattrs support on osx ... @ build, i note complaint abt a missing yodl2man, which originates with YODL. YODL, then requires icmake. as neither is available on osx, it's src build time. on building debian's icmake (alrea...

...ed a new protocol version (30). If the remote protocol version is older than 30, rsync behaves as before. The changes made to the reference version are small and kept in accordance with the original style. The affected files are: flist.c generator.c options.c proto.h rsync.1 rsync.c rsync.h rsync3.txt sender.c and util.c Please find the corresponding patch attached to this email. We have thouroughly tested our new protocol under Linux and also compiled it under Unix (Aix). It works as expected under Linux while some of the changes were redundant under Unix. We consider the preservation of t...

...om> is much faster. If your >> OpenSSH is too old for chacha to be the default then aes128-ctr was the >> default anyway. >> >> On 03/21/2018 09:49 AM, Jayce Piel via rsync wrote: >>> >>> Here are my options : >>> >>> /usr/local/bin/rsync3 --rsync-path=/usr/local/bin/rsync3 -aHXxvE --stats >>> --numeric-ids --delete-excluded --delete-before --human-readable >>> —rsh="ssh -T -c aes128-ctr -o Compression=no -x" -z >>> --skip-compress=gz/bz2/jpg/jpeg/ogg/mp3/mp4/mov/avi/vmdk/vmem --inplace >>&g...

...sync (for architecture x86_64): Mach-O 64-bit executable x86_64 -rwxr-xr-x 1 pepi staff 2535144 18 Apr 22:49 rsync When created this way, rsync running on an intel Core2Duo based Mac will not preserve creation date/time. I've tested this with backupbouncer 0.1.3: ------------------ rsync3-maclemon-beta ------------------ This copier produced log output in: /Volumes/Dst/81-rsync3-maclemon-beta/log Verifying: basic-permissions ... ok (Critical) Verifying: timestamps ... ok (Critical) Verifying: symlinks ... ok (Critical) Verifying: symlink-ownership ......

An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20180323/66c46d5a/attachment.html>

...enhancement Priority: P5 Component: core Assignee: wayned at samba.org Reporter: RutleCorps at gmail.com QA Contact: rsync-qa at samba.org Client version 3.1.2 Server version 3.0.9 When using rsync 3.1.2 gives the error: /usr/local/s3rsync/prod-ssh-rsync3: invalid rsync-command syntax or options By removing options, I was able to track the problem to the —stats flag. It would be useful if the error message could report that —stats was the cause of the error. -- You are receiving this mail because: You are the QA Contact for the bug.

...ror: error in rsync protocol data stream (code 12) at /src/ rsync-3.0.5/io.c(600) [sender=3.0.5] I'm using the patch below as a temporary workaround, but I'm curious if anyone has insight as to why rsyserr might not be printing these messages from the receiver. Mike diff -Naur -X rsync3/_build/diff_ignore rsync-3.0.5_base/receiver.c rsync-3.0.5/receiver.c --- rsync-3.0.5_base/receiver.c 2008-11-15 16:49:28.000000000 -0600 +++ rsync-3.0.5/receiver.c 2009-03-10 22:18:20.000000000 -0500 @@ -297,6 +315,16 @@ if (fd != -1 && offset > 0 && sparse_end(fd) != 0) {...

...: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: RutleCorps at gmail.com QAContact: rsync-qa at samba.org --stats in 3.1.0 when connecting to an rsync 3.0.5 error is: /usr/local/s3rsync/prod-ssh-rsync3: invalid rsync-command syntax or options -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

Hi! I've just tried to do a backup of a machine with rsync. While doing this (I was reading emails:-) I noted that mbox for mbox, I had no longe new mails, but I've never read off these mailboxes lately... This seemed to be a st_atime problem, and indeed, I could verify that. This is what I used for backup: rsync --archive \ --recursive \