similar to: DO NOT REPLY [Bug 5235] New: buffer overflow in receive_file_entry

https://bugzilla.samba.org/show_bug.cgi?id=3649 Summary: buffer overflow in receive_file_entry Product: rsync Version: 2.6.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: sambesselink@planet.nl

I have rsync 2.6.6 on unix source to a cygwin setup on a Windows 2003 server. Was working well, then I moved a folder down one subdirectory and started getting the following. I assume this means it is having problems with the length of the file name? I have the same problem with long file names using cwRsync. Are there any options other than modifying the file names? backup# ./820.remote-backup

https://bugzilla.samba.org/show_bug.cgi?id=2784 Summary: rsync gives following error: buffer overflow in receive_file_entry Product: rsync Version: 2.6.3 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=2785 Summary: rsync gives following error: buffer overflow in receive_file_entry Product: rsync Version: 2.6.3 Platform: All OS/Version: All Status: NEW Severity: major Priority: P3 Component: core AssignedTo: wayned@samba.org

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

As those of you who watch CVS will be aware Wayne has been making progress in reducing memory requirements of rsync. Much of what he has done has been the product of discussions between he and myself that started a month ago with John Van Essen. Most recently Wayne has changed how the file_struct and its associated data are allocated, eliminating the string areas. Most of these changes have been

Hi, Rsync 3.0.5 on both sides. receiver is Open Solaris and sender is Linux. I got a nested directory - relatively depth but still it should work. It fails instead. sending daemon args: --server --sender -vvlWHogDtpre.is --ignore-errors --numeric-ids --inplace . TEST/ receiving incremental file list delta-transmission disabled for local transfer or --whole-file [...] overflow: xflags=0x7a

has anyone seen this error: ns1: /acct/peter> rsync ns1.pad.com::acct overflow: flags=0xe8 l1=3 l2=20709376 lastname=. ERROR: buffer overflow in receive_file_entry rsync error: error allocating core memory buffers (code 22) at util.c(238) ns1: /acct/peter> -- Peter Dominguez 72 Belvedere Dr Yonkers, NY 10705-2814 USA Tel: 914-423-4000 Fax: 914-423-8640 Email: peter@pad.com

Hi, I have two identical servers running Mandrake 10.0 + many bugfixes. I installed the plain rsync 2.6.3 (and after that the last cvs checkout, but with identical results) and configured rsync as xinetd daemon on one of the two, rsync as client on the other. This is the result: [root@server rsync-2.4.4]# rsync -avz server::sitis/mydir/ receiving file list ... overflow: flags=0xb6ee l1=21

As you all know, rsync doesn't have any special handling for Mac OS X HFS+ resource forks. Kevin Boyd made RsyncX and rsync_hfs, to address this gap, but they only work when the destination filesystem is also HFS+. I haven't been able to find any references to an rsync that is capable of syncing from HFS+ to UFS (etc). The only solutions I've seen involve lots of preprocessing

https://bugzilla.samba.org/show_bug.cgi?id=8001 Summary: buffer overflow in recv_file_entry (maxpathlen doesn't works) Product: rsync Version: 3.0.8 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

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

Hello, I'm looking for some possible solutions to the out of memory problem when dealing with very large directory trees. Client: linux-2.4.20 Server: HP-UX 11.11 rsync version: 2.6.2 Directory size: 400Gbytes number of files: 3273133 rsync cmd: rsync -avRx --progress --stats --numeric-ids --blocking-io --delete -e ssh hp-ux.server:/path /local/linux/ It seems to fail after consuming

I believe this post I found is related to a problem I'm having with long files names...I would like to use cwRsync, does my problem suggest this is still happening and has not been addressed? http://lists.samba.org/archive/rsync/2005-April/012117.html However, I have long file name issues using rsync 2.6.6 from a BSD server to the default Cygwin rsync 2.6.6. Should I (and how do I) apply

Hello, I've had some problems using rsync to transfer directories with more than 3 million files. Here's the error message from rsync: <snip> ERROR: out of memory in receive_file_entry rsync error: error allocating core memory buffers (code 22) at util.c(116) rsync: connection unexpectedly closed (63453387 bytes read so far) rsync error: error in rsync protocol data stream (code

I'm getting a SEGV on a FreeBSD 4.8-STABLE box. The client is Solaris 9/SPARC. Both boxes run 2.6.2. The command I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb> bt #0 0x280faf0d in strncmp () from /usr/lib/libc.so.4 #1 0x7 in ?? () #2

This patch adds some queue limit parameters into block drive. And inits them for sg block drive. Some interfaces are also added for accessing them. Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com> --- block/raw-posix.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++ block_int.h | 4 +++ blockdev.c | 15 +++++++++++++ hw/block-common.h | 3 ++ 4 files

This patch adds some queue limit parameters into block drive. And inits them for sg block drive. Some interfaces are also added for accessing them. Signed-off-by: Cong Meng <mc at linux.vnet.ibm.com> --- block/raw-posix.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++++++ block_int.h | 4 +++ blockdev.c | 15 +++++++++++++ hw/block-common.h | 3 ++ 4 files

I was sent this from Mark Miller. Should we be using MAXPATHLEN instead of PATH_MAX in the upstream tree? Not all systems define PATH_MAX. - Ben --- sftp-int.c.orig Sat Feb 10 13:56:08 2001 +++ sftp-int.c Sun Feb 11 23:33:26 2001 @@ -435,5 +435,5 @@ unsigned long n_arg; Attrib a, *aa; - char path_buf[PATH_MAX]; + char path_buf[MAXPATHLEN]; path1 =

Yo Andrew! What version of Openssh are you trying? RGDS GARY On Mon, 12 Jun 2000, Andrew McGill wrote: > Date: Mon, 12 Jun 2000 15:26:53 +0200 > From: Andrew McGill <andrewm at datrix.co.za> > To: djm at ibs.com.au > Cc: gem at rellim.com > Subject: Openssh on SCO Openserver Release 5 > > Hi there > > Your e-mail address appears in the README for openssh,