similar to: batch mode maintainability

rsync+ is ready to go onto HEAD. Could Jos or somebody else who's used the feature before please prepare a few paragraphs for the manpage explaining how they work? Either send a patch to the .yo files or just plain text. Thanks, -- Martin

Chris, to put things in the right prespective, you should read (if you haven't done so already) the original paper describing the design behind batch mode. The design and implementation of this functionality goes back to a project called the Internet2 Distributed Storage Infrastructure (I2-DSI). As part of that project, the authors created a modified version of rsync (called rsync+)

Hi everybody! Now that RSYNC has RSYNC+ included a good usage would be to use RSYNC+ to gather update-date, then multicast that on your hosts and process it. So my question is: does anyone know of a product which does reliable multicasting? (source available would be preferred) Simple pointers are appreciated; if noone has one I'm thinking about writing one myself. Thanks for all help!

Bert, Hi. If you are still interested in your rsync+ project, changes for which have evidently been (and are, perhaps, still being?) submitted to the official, upstream rsync version, you may want to add the following feature, proffered below, in order to conduce a little greater batch mode usage flexibility primarily for those with above average security concerns. Currently (at least in the

Hi! I try to use batch mode to send only the difference between two packed CDs by email over a slow line. I create the diff with: rsync -avvv --write-batch=rs CD-ROM-V6.6.32.zip CD-ROM-V6.6.31.zip where alfred:/Auslieferung/CD # l -n -rw-r--r-- 1 0 0 453248121 Sep 2 16:22 CD-ROM-V6.6.31.zip -rw-r--r-- 1 0 0 407416499 Sep 29 13:39 CD-ROM-V6.6.32.zip resulting

This is a patch to add an --rsync-exclude option to rsync-2.5.6cvs. File names in .rsync- (or .rsync+) are excluded (or included) from the file lists associated with the current directory and all of its subdirectories. This has advantages over --cvs-exclude for backing up large file systems since the .cvsignore files only apply to the current directory: unless the .cvsignore restrictions apply

Here's the latest version of the batch mode cleanup patch. Index: batch.c =================================================================== RCS file: /cvsroot/rsync/batch.c,v retrieving revision 1.12 diff -u -r1.12 batch.c --- batch.c 24 Jan 2002 08:09:46 -0000 1.12 +++ batch.c 6 Feb 2002 19:47:57 -0000 @@ -8,55 +8,38 @@ #include "rsync.h" #include <time.h> -char

Hello ! I`m trying to find a way to use lzo compression for the data being transferred by rsync. rsync only supports gzip (or maybe ssh -c, which is also zlib), which gives cpu intensive workload - and this cannot be exchanged by a commandline param like we have with tar (--use-compress-program=....) i like to use lzo because it does much faster compression than gzip. I read the following in

I needed a tool to produce diffs of binary volumes, and to apply them as patches accordingly. So I tried the 'batch mode' that was added to rsync, but it invariably segfaulted on reading the batches... $ sh foo.rsync_argvs foo.rsync_argvs: line 1: 8971 Segmentation fault rsync -a -v --stats --read-batch=foo ${1:-FOO} rsync: error writing 64 unbuffered bytes - exiting: Broken pipe

Hello, I want to use the --read/write-batch options, but i have problems to do so. The shell script [1] leads to the following error: [sender] expand file_list to 131072 bytes, did move delta-transmission disabled for local transfer or --whole-file file1 rsync: writefd_unbuffered failed to write 64 bytes: phase "unknown": Daten?bergabe unterbrochen (broken pipe) rsync error: error in

> Just curious: what about the rsync+ patch? Thanks for the reminder. I've just committed Jos's rsync+ patch onto the "branch_mbp_rsyncplus_merge" branch. If it works OK and nobody screams I will move it across onto the main tree tomorrow or Wednesday. I see the patch doesn't add documentation about the new options to the man page, so we should fix that in the future.

Currently the --write-batch option in addition to creating the batch files also syncs the target tree. I'm not sure whether this is always desired. So far the only way I have been able to come up with to prevent the target tree from being populated is the patch below; however, the top-level target directory is still created, so it is not complete. Does this sound like a worthwile addition to

Hi all, I was wondering if it will require any major rewrites of the daemon/client to include limits on the data transfer rate ? Alexei.

OK. I got the rsync CVS code and compiled under Linux. That did the job, but only with --no-whole-file because of the local transfer. I then tried to read-batch... under Windows / Cygwin with the current Cygwin rsync. That didn't work - as expected. After compiling again under cygwin it worked! I can now create a diff from a new CD to the version before and send the diff files by email. On

On Mon, Oct 13, 2014 at 7:01 PM, Eric Christopher <echristo at gmail.com> wrote: > On Mon, Oct 13, 2014 at 6:59 PM, Sean Silva <chisophugis at gmail.com> wrote: > > For those interested, I've attached some pie charts based on Duncan's > data > > in one of the other posts; successive slides break down the usage > > increasingly finely. To my

For those interested, I've attached some pie charts based on Duncan's data in one of the other posts; successive slides break down the usage increasingly finely. To my understanding, they represent the number of Value's (and subclasses) allocated. On Mon, Oct 13, 2014 at 3:02 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > In r219010, I merged integer and

> On Oct 13, 2014, at 6:59 PM, Sean Silva <chisophugis at gmail.com> wrote: > > Stupid question, but when I was working on LTO last Summer the primary culprit for excessive memory use was due to us not being smart when linking the IR together (Espindola would know more details). Do we still have that problem? For starters, how does the memory usage of just llvm-link compare to the

Well, here's rsync 2.4.7 preview 1: rsync://va.samba.org/ftp/rsync/preview/rsync-2.4.7pre1.tar.bz2 http://va.samba.org/ftp/rsync/preview/rsync-2.4.7pre1.tar.bz2 You need bunzip2 to decompress these files: http://freshmeat.net/projects/bzip2 The change list is below. Please, do try this out and let us know either if it works for you or if it does not. We need both kinds of

I'm using rsync version 2.5.7, and I see this behavior with Debian and Redhat installations. This works: rsync rsync://mirror.physics.ncsu.edu/redhat/linux/updates/9/en/os/i386/zebra* ./temp But this doesn't: rsync --write-batch=mytest rsync://mirror.physics.ncsu.edu/redhat/linux/updates/9/en/os/i386/zebra* ./temp I've also tried with my normal args, like "-vvvvv --progress -t

Hi, Whenever i am using the command rsync --write-batch -av --stats `cat $1` -e ssh user@remote machine:/destination/ This is writing rsync_argvs files in the home directory as well as to the destination directory. Can anyone give me any idea as how to prevent the writing of rsync_argvs files in the home directory which is of no use. Regards, Surabhi. > ---------- > From: