Displaying 20 results from an estimated 3000 matches similar to: "rsync server over SSH [includes code patches]"
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
2003 Jul 24
0
(no subject)
Here is a diff which should allow applying batch updates remotely ( as
apposed to copying the batch files to the remote server and running rsync
there ).
Eg
rsync --write-batch=test src dst1::dst
rsync --read-batch=test dst2::dst
Oli Dewdney
diff -E -B -c -r rsync-2.5.6/flist.c rsync-2.5.6-remotebatch/flist.c
*** rsync-2.5.6/flist.c Sat Jan 18 18:00:23 2003
---
2003 Feb 22
1
rsync ported to BeOS-bone
Hello, here is a preliminary patch allowing rsync 2.5.6
to compile in BeOS (using the new BONE networking stack).
Some explanations:
- BeOS doesn't have chroot(),
- the BONE networking stack export legacy network function
for old apps in libnet.so (linked to by default), so it's
necessary to force linking to the new libraries for things
to work. I've yet to get inet_ntop() to be
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 Jan 27
1
Differentiating debug messages from both sides
Some of the debug messages that rsync outputs (when verbose >= 2) can
occur on both sides of the connection. This makes it hard to know which
program is saying what. Some debug messages deal with this by
outputting a "[PID]" string at the start of the message. Unfortunately,
the startup message that tells us which pid is which is only output when
verbose >= 3, so there's a
2003 Jan 03
1
[Fwd: Re: rsync windows -> unix still hanging :(]
Author of the message didn't include rsync@lists.samba.org in the reply,
and I think this message is in topic.
-------- Original Message --------
Subject: Re: rsync windows -> unix still hanging :(
Date: Mon, 30 Dec 2002 17:24:47 -0800
From: Jim Kleckner <jek_subs@kleckner.net>
To: Mike Rubel <mrubel@galcit.caltech.edu>
CC: cygwin@cygwin.com
References:
2003 Mar 23
1
[RFC] dynamic checksum size
Currently rsync has a bit of a problem with very large
files. Dynamic block sizes were introduced to try handle that
automatically if the user didn't specify a block size.
Unfortunately that isn't enough and the block size would
need to grow faster than the file. Besides, overly large block
sizes mean large amounts of data need to be copied even for
small changes.
The maths indicate
2001 Aug 22
1
@RSYNC EXIT / @RSYNC EOF
tridge and Wayne in particular:
I checked in this patch, which is meant to consolidate the ones from
both of you for handling EOF in a modules list. The idea is that we
need to handle servers that just close the socket rather than sending
a nice ending token, but we want to keep EOF detection on in general.
(The IO code is such a mess!)
--
Martin
Index: clientserver.c
2002 Feb 24
2
Write-only option
Hi!
I am doing backups from a number of machines to an rsync server. For some
time I was trying to come up with a solution, which would prevent users
from peeking at each other's files, which are backed up. Finally, I've
hacked rsync, introducing a new option "write only" for rsyncd.conf. When
set to true, this option forbids the transfers from server to the client,
thus solving
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
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
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
2004 Jan 17
1
--delete-sent-files (AKA --move-files)
Yes, it's time once again to return to the subject of moving files.
With the recent changes to the communications code between the receiver
and the generator, there is now a non-clogging channel that we can use
to signal the sender when a file has been successfully transferred,
which allows us delete the original for all transferred files. I have
in the past waffled on whether this feature
2004 Feb 12
1
[PATCH] write only
We use rsync to provide an rsync share on a linux server with a javascript
program on Windows clients which ensures all client data is backed up each
morning.
After making no progress with my posting last month regarding making a module
upload only to prevent someone from manually downloading the rsync share
obtaining other users work (exclude = * wasn't possible because we need
--delete to
2004 Jan 26
1
patch for linux capabilities
I was wondering if it might be possible for an rsync developer to
look over the attached patch (tested on Linux 2.4.24 against the
rsync-2.6.0 release), and offer suggestions on how I could improve it.
Basically I want to use Linux finer grained capabilities to retain
only CAP_SYS_CHROOT & CAP_DAC_READ_SEARCH when rsync drops root
privs. That way I can take whole system backups as a (mostly)
2002 Dec 09
2
Rsync performance increase through buffering
I've been studying the read and write buffering in rsync and it turns
out most I/O is done just a couple of bytes at a time. This means there
are lots of system calls, and also most network traffic comprises lots
of small packets. The behavior is most extreme when sending/receiving
file deltas of identical files.
The main case where I/O is buffered is writes from the server (when
io
2004 Feb 09
1
[patch] Add `--link-by-hash' option.
This patch adds the --link-by-hash=DIR option, which hard links received
files in a link farm arranged by MD4 file hash. The result is that the system
will only store one copy of the unique contents of each file, regardless of
the file's name.
Anyone have an example of an MD4 collision so I can test that case? :)
Patch Summary:
-1 +1 Makefile.in
-0 +304 hashlink.c (new)
2009 Nov 04
0
PATCH: fast copy of files in local server mode
Dear List,
the attached patch makes rsync of local folders almost as fast as cp.
when rsync client and server has detected that they are working in
local_server mode,
they use local_socket, a unix domain socket pair, to pass the file
descriptors of the synced files.
the server uses the file descriptor it receives from the client to fast copy
from src to dst file.
on completion of every file fast
2004 May 29
1
[patch] Filename conversion
Hi,
One feature missing from rsync, and requested on this list before, is
on-the-fly conversion of filename character encoding. For example, I
often need to sync files having Hebrew filenames from a UTF-8 system
(Linux) to an ISO8859-8 system (Cygwin on Windows 2000 using the
non-Unicode Win32 interface). Other circumstances surely abound.
Attached is a patch against rsync 2.6.2 that adds an
2004 Feb 23
0
[patch] Add `--link-by-hash' option (rev 4).
This patch adds the --link-by-hash=DIR option, which hard links received
files in a link farm arranged by MD4 file hash. The result is that the system
will only store one copy of the unique contents of each file, regardless of
the file's name.
(rev 4)
* Updated for committed robust_rename() patch, other changes in CVS.
(rev 3)
* Don't link empty files.
* Roll over to new file when