similar to: rsync+ patch

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+)

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

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

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

> 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.

When I dont specify --block-size but have --write-batch=xxx, I get a xxx.rsync_csum file that is 76 Kbytes in size. The size of the file varies as the size of the "reference" file is varied. --stats showed matched data that is roughly 6 block lengths based on the square root of the newer file. I copy the original data back to the target directory so that I can repeat the experiment. I

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

I'm having second thoughts about merging the rsync+ / batch mode patch into the main rsync release. It adds a lot of extra paths to the code. I can see it will be useful for a few people, but I'm not sure it's sufficiently general to justify being there. Dave? -- Martin

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 all, I'm running the following rsync job via cron: rsync --recursive --compress --human-readable --progress --update --perms --chmod=a-w -e "ssh -i /rsync-key" user@host:/source_dir/ /target_dir rsync: failed to set permissions on "/target_dir/.": Operation not permitted (1) rsync: failed to modify permissions on "/target_dir/.": Operation not permitted (1)

> Vladimir, > > I took a *very quick* look at your patch. I won't be able to look at it in > more detail until this weekend, but perhaps you can address a couple of > concerns: > > 1. I don't understand the need for LLVMToolDirSlash. This seems like a > gratuitous change to me. If LLVM_OBJ_ROOT (with LLVM_SRC_ROOT) and LLVM_ROOT both not set without

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!

>> Before this change is committed, you need to test that all our scenarios, >> in each combination: >> >> 1. Both with and without OBJ_DIR == SRC_DIR >> 2. Single and Parallel builds >> 3. Building LLVM versus building a project (and now building from >> installed) > ok, will do... > > I found some bugs in my patch and then I will send updated

Hi, What determines the umask of sieve_pipe_bin_dir scripts ? The results from my script are always being set to 0600. My script is simple and shown below, even if I adjust the right line to add " && chmod 644", the actual resulting file still remains at 0600 ?!? #!/bin/bash # Usage: imapsieve_copy <email> <spam|ham> MSG_USER="$1" MSG_TYPE="$2"

Hi all, I thought I'd share I script I made (based on some of Leif's works) that lets you download, compile and install Asterisk all in one go; and then removed the dev tools used. We use it quite a bit to provision systems using Ansible, but it is easier than remembering everything every time even if you are using a shell. At the moment I have scripts for Centos 7 and Asterisk 13, but

Otherwise, automake will fail to process vivified/code/Makefile.am --- configure.ac | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/configure.ac b/configure.ac index a3e186b..0e28374 100644 --- a/configure.ac +++ b/configure.ac @@ -300,6 +300,7 @@ else AC_MSG_NOTICE([Vivified was not enabled.]) fi AM_CONDITIONAL(HAVE_VIVI, [test "x$HAVE_VIVI" = xyes])

I am using llvm-project compiling risc-v programs. llvm-project version:dd8a2013dc1804be1b7d9cffacad2e984300bd22 Instructons to build LLVM+clang: ``` cmake -G Ninja -DCMAKE_INSTALL_PREFIX=/home/llvm/workspace/llvm/llvm-project/llvm_install -DCMAKE_BUILD_TYPE="Release" -DDEFAULT_SYSROOT="/home/llvm/workspace/riscv/riscv-tc-20200220/bin/riscv32-unknown-elf"

Command like this: rsync -rxlupogtSvve ssh $src_host:"/home/wss_disk/calendar.data/'Conference Calls'" $targ_dir works fine with blanks embeded in the file name. When I try to script it like this: COM='`find '$src_dir' -mtime -'$days' -type f `' rsync -rxlupogtSvve ssh $src_host:"$COM" $targ_dir works fine on regular filenames,

Hi, Here is the problem (syscall.c, function do_open) on NT, Win2K, WinXP, with stripped "/" for UNC path convention, detected in release 2.5.5, 2.5.6: int do_open(char *pathname, int flags, mode_t mode) { if (flags != O_RDONLY) { if (dry_run) return -1; CHECK_RO } #ifdef O_BINARY /* for Windows */ flags |= O_BINARY; #endif /* some systems can't handle a double / */

*1. I have searched the access/setting of LLVMCC_EMITIR_FLAG in the build directory, recursively, and all the output is what I pasted in last email (just the same to the that in source directory). Maybe the configure failed to do it. My command list for building the test suit is as followings:* *(1) cd ~/SRC_DIR/llvm/projects* *(2) svn co http://llvm.org/svn/llvm-project/test-suite/trunk