Displaying 20 results from an estimated 300 matches similar to: "batch diffs"
2002 Feb 07
1
Latest version of the batch mode cleanup patch
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
2004 Jun 17
1
[PATCH] make write_batch local
Wayne,
It's taken a little while for me to get more familiar with the
code, but I think I've reached a good breakpoint in improving
batch-mode. Let me highlight some of the changes in the
attached patch:
* --write-batch and --read-batch arguments are no longer passed
from client to server. This fixes the current problem
that causes the server threads to die when the client
2003 Mar 08
1
[patch] rsync over existing I/O connections (new feature)
Hello,
I wrote this patch that allows you to run rsync over an existing I/O
connection, instead of creating a new rsh or socket connection.
For example, I have a client and server that talk over ssh via a simple
custom protocol. I want to use the existing ssh connection to transfer files,
but I want the flexibility of rsync to do it.
With this patch, I can do the following in my client
2001 Aug 06
1
merge rsync+ into rsync (was Re: rsync-2.4.7 NEWS file)
> 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.
2002 Jul 28
0
Ex-Bug Report: -z option
Since writing this I've recompiled with zlib 1.1.4 and everything appears
smooth. Since this is intermittant, I'll send it off anyways in the hops that
someone else may see it. It also *might* apply to the "known issues"
entry about "unexpected close." (Similar symptoms, but it may just be a shared
codepath on the messages. Note that the dumped len in my output(4)
2003 Nov 17
0
[PATCH] --source-filter && --dest-filter for rsync 2.5.6
Hi,
I needed to filter content of files (encrypt), before they are sent over the network to backup server.
The easiest way to do this was modifying Kyle Jones's "--dest-filter" patch.
Somebody was asking there this feature in the past, so I'm sending this patch to list.
Implementation details:
-filtering disables rsync alogrithm
-source filter makes temporary files in /tmp
2004 Jul 12
2
[PATCH] Batch-mode rewrite
Wayne,
Please consider the attached patch. This applies to the current
CVS, and is independant of patches/local-batch.diff. As a matter of
fact, I'm sure it would conflict heavily with local-batch.diff.
This version of batch mode has a couple distinguishing features:
Write-batch records (almost) the entire sender side of the conversation
into one file. ("Almost" because it has
2002 Mar 15
2
rsync: transmitting always whole files
Hi,
I use rsync in the following way to update some remote files over a low
bandwidth line:
rsync -v -r -z -t -p <local dir> <user>@<host>:<dir on host>
After updating from rsync 2.5.2 to 2.5.4 I noticed that modified files are
always copied completely. The problem seems to be related to the new (in
2.5.3) option -no-whole-file. The global variable whole_file is
2002 Aug 05
5
[patch] read-devices
Greetings,
I'd like to propose a new option to rsync, which causes it to read
device files as if they were regular files. This includes pipes,
character devices and block devices (I'm not sure about sockets). The
main motivation is cases where you need to synchronize a large amount of
data that is not available as regular files, as in the following scenarios:
* Keep a copy of a block
2003 Sep 30
2
problem with batch mode:
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
2004 Sep 23
1
[Bug 1812] fuzzy not working in 2.6.3-pre{1,2}
https://bugzilla.samba.org/show_bug.cgi?id=1812
wayned@samba.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From wayned@samba.org 2004-09-23 08:47
2002 Mar 28
1
(no subject)
There are quite a few compilation warnings from rsync-2.5.5rc1 that
could be eliminated by code cleanup.
gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c main.c -o main.o
main.c: In function `start_client':
main.c:665: warning: unused variable `write_batch'
main.c:664: warning: unused variable `whole_file'
These warnings will go away when the two variables are properly
bracketed
2002 Oct 07
1
building problem with rsync up to 2.5.5
Heya All,
Im having difficulties compiling rsync. when i run 'make' the
build errors out on me. I run configure without any fancy
options. The same goes for the make command. I have had this
error, or a similar one since version 2.5.1 op to at least
v2.5.5
I am using "-O3 -mcpu=i686 -march=i686" as additional compiler
flags, however removing them does not make difference.
2001 Dec 08
0
Should --write-batch always sync the target tree?
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
2004 Jan 24
2
[PATCH] --links-depth for rsync
Hello,
about a year ago I ran into situation where there's a "metadirectory"
containing directories and symlinks to files. There was a need to mirror
the contents of files and directories gathered via symlinks to this
metadirectory, regular mirroring of the tree wouldn't do any good.
The attached patch gives the user ability to define how many symbolic
links rsync should follow
2004 Jun 21
2
problems with --read-batch and --write-batch with --files-from
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
2003 Mar 30
1
[RFC][patch] dynamic rolling block and sum sizes II
Mark II of the patch set.
The first patch (dynsumlen2.patch) increments the protocol
version to support per-file dynamic block checksum sizes.
It is a prerequisite for varsumlen2.patch.
varsumlen2.patch implements per-file dynamic block and checksum
sizes.
The current block size calculation only applies to files
between 7MB and 160MB setting the block size to 1/10,0000 of
the file length for a
2005 Mar 21
4
Patch: Offline transfer mode
Hi All,
Here's an rsync patch which adds an --offline flag, letting you transfer
changed blocks via removable media, while still comparing checksums via
the net. I expect this could be very popular for the growing number of
people who want to do disk-based offsite backups, which is what I needed
it for.
It took me longer than I hoped, but still only several hours to work
this out -- it
2004 Apr 30
1
--write-batch just hangs?
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
2004 Jun 18
2
possible writefd_unbuffered error; what am I screwing up this time
I am trying to execute rsync manually at a "remote" server to test out --read-batch execution.
I created the batch files on another server and then rcp'ed them to the "remote" server. I had some issues of not having the
correct working directory on the remote system when I did an rsh "remote" rsync --read-batch ...... so I opened a telnet session
on the remote