Displaying 20 results from an estimated 400 matches similar to: "Rsync read_int questions"
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:
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 06
0
rsync hangs in read_int (generator.c line 498)
Hello
I'm having a heck of a time rsync'ing (is that the proper conjugation?
:)) between two Cygwin machines. I have three directory trees that are
"exposed" via rsynch. Two of the three have a very shallow structure,
and they work fine. The third, however, has a fairly deep structure and
many more files than the other two, and rsync'ing this directory causes
a hang on
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.
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 Jan 05
2
buffer overflow in recv_exclude_list using rsync under windows?
Hi,
First post to the list, so please feel free to set me straight if I'm not
following some protocol or other :o)
We need to use rsync to send files to a client, being a Windows user, we
decided to try both the cwrsync implementation and also a straight
cygwin/rsync install. I'm experiencing the following errors:
using cygwin implementation:
$ sh clientupload.sh
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
2003 Mar 22
2
[RFC] protocol version
I'm in the midst of coding a patch set for consideration
that will bump the protocol version and have a couple of
observations.
The current minimum backwards-compatible protocol is 15
but we have code that checks for protocol versions as old as
12. If someone else doesn't beat me to it i'm considering
cleaning out the pre-15 compatibility code. A backwards
compatibility patch could
2003 Oct 05
2
Possible security hole
Maybe security related mails should be sent elsewhere? I didn't notice
any so here it goes:
sender.c:receive_sums()
s->count = read_int(f);
..
s->sums = (struct sum_buf *)malloc(sizeof(s->sums[0])*s->count);
if (!s->sums) out_of_memory("receive_sums");
for (i=0; i < (int) s->count;i++) {
s->sums[i].sum1 = read_int(f);
2001 Sep 05
2
Feedback on 2.4.7pre1
FYI,
We've been using the 2.4.7pre1 release for several days now, with nary a
hang problem. We haven't seen the EOF bug at all, which was what we
upgraded for. This is with transfers of as much as 50GB to set up an
initial mirror.
The only thing we did was set timeout=0 -- which I guess is unnecessary.
The semantics of this flag are a bit unclear. We thought was 'time since
2002 Nov 11
0
Regular Expression support
I have added regular expression support using a POSIX implementation.
The patch (against 2.5.5) is attached.
The implementation is simple and follows the same mechanism that is
implemented for normal searches.
I added these command line arguments:
--rexclude=PATTERN exclude files matching regexp PATTERN
--rexclude-from=FILE exclude regexp patterns listed in FILE
--rinclude=PATTERN
2001 Dec 18
3
rsync hang, more details [LONG]
rsync 2.5.0 still has a bug where it hangs under some circumstances.
The hang is beyond my abilities to track down. I'll keep trying,
though, but here are details in case they're of use to anyone else:
- Code configured & built on Solaris 2.5.1.
- Same binary run on Solaris 2.5.1 (client) and 2.8 (server).
- Using rsh transport, but also fails with ssh
- Does not fail with
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
2015 Dec 26
0
About data/token send/receive protocol part and more
Dear rsync experts,
I'd like to ask you a couple of questions.
***** 1. *****
If I'd like to send additional metadata for each block, what would be the easiest and less intrusive way to do this? The following seems to work:
----------------------------------------------------------------------------
diff -rupN ../rsync.git/token.c ./token.c
--- ../rsync.git/token.c 2015-11-03
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
---
2002 Jan 13
0
rsynd-2.5.1 / io.c patches
Platform: Compaq OpenVMS Alpha 7.3
Compiler: Compaq C T6.5
The following patch resolves compile problems with the IO.C module.
The (char) type was being used where (void) was more appropriate based
on the actual use of the code.
The (char) type was also being used where the usage was actually an
(unsigned char).
const qualifiers were added to improve compile efficiency.
EAGLE> type
2003 May 20
0
patch for better handling of write failures (disk full)
I've been having problems trying to sync two small partitions (128MB)
that may be near to full.
If rsync gets a write error (such as is caused when you fill up a
partition) during a sync without the use of "-T", it will stop with
this error:
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
rsync error: error in rsync protocol data stream
2004 Apr 10
0
patches for copying atimes
Hi.
Here's a patch for copying the atimes of files when -t/--times is
given. I bumped the protocol to 29 since it sends more data over the
wire. It obviously does not send the atime if it's sending data to an
older rsync version.
It passes all the tests (including the added atime.test) for me on a:
Linux Debian/3.0 gcc 2.95.4 (debian), glibc 2.2.5 system.
Any questions/feedback? I
2006 Jan 24
1
propagate atimes with rsync-2.6.6 (fwd)
Dear Martin Pool.
We regularly use rsync for making backups of our file systems but we have
noticed that the atimes are not transferred with the files and are also
always updated on the sender's side. Therefore, we have created a modified
version of rsync based on rsync-2.6.6 protocol version 29 which transfers
the access times with the transferred files and also allows to preserve
the access
2017 Apr 14
4
rsync buffer overflow detected
Hello!
I use rsync from python on my Debian Jessie amd64 and get this error:
*** buffer overflow detected ***: <snip>/rsync terminated
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x731af)[0x7ffff78971af]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7ffff791caa7]
/lib/x86_64-linux-gnu/libc.so.6(+0xf6cc0)[0x7ffff791acc0]