similar to: rsync limit to file size/file count

Hi, folks. I've started getting these errors from rsync, and any help would be appreciated: >ERROR: out of memory in string_area_new buffer >rsync error: error allocating core memory buffers (code 22) at util.c(115) >ERROR: out of memory in string_area_new buffer >rsync error: error allocating core memory buffers (code 22) at util.c(115) >ERROR: out of memory in

Attention rsync list members, Do not open up the attachment that comes along with this e-mail because it is a virus. Is there anyway you can stop sending these e-mails to everybody on the list? I've received maybe 3 or 4 of them since yesterday. Regards, Eric

Hi, I have 2 linux machines, SOURCE and DEST on a network. I create some snapshots of the file structure on SOURCE and these snapshots have extended attributes. I want to copy the snapshots from SOURCE over to DEST over the network, but I don't want to lose the information on the extended attributes. Is there a way to do this using the samba protocol? Or do I have to modify the source code to

Hello all, I saw on the Release notes that 2.6.0 is using protocol version 27 which is different than 2.5.7 and 2.5.6. I did a quick peak through the rest of the release notes and quickly browsed the archives on the list and I didn't see any notes on how well 2.6.0 works with older versions of rsync. At our site, we do have 2.5.7 and 2.5.6 installed. Are there any documented problems when

In case others find this of value, I wrote a patch to rsync 2.5.6 to give rsync in --daemon mode the ability to run a pre-transfer and post-transfer command. These options handle our need to prepare a server to receive files and to do some processing after receiving files. The options for /etc/rsyncd.conf are pretransfer script = /some/command/to/run posttransfer script =

Hi, I just subscribe to ask you a question about patterns in exclude-include files. I just want some folders to be rsynced to a remote machine. What I tried is : IncludeFile ------------------------- /etc/ /var/lib/zope/ - /* ----------------------- result of $$ rsync -avvrn --delete --delete-excluded --include-from=/backup-include -e ssh / /backup is expand file_list to 4000 bytes, did move

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

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

I'd like to suggest that this is now a great time to create two separate cvs branches for the rsync product. One, which I'll tentatively call 2_5, would hold the version of the code that has been released to the world as 2.5.6. The other, which I'll tentatively call head, would hold the development activity leading up to the next field release. I'm not bound to these names, but I

I am looking to upgrade to latest version of rsync. However there are some critical bug fixes (for my needs) that have been commited to CVS post 2.5.6 release. Can anyone tell me how i can find out the release schedule for 2.5.7? I looked around at rsync home page and did not see how i can access schedule/timeline for official releases. I can work with latest in CVS if the release date is too

On Mon, 10 Nov 2003, Wayne Davison <wayned@samba.org>?wrote: > >?... This fix is also in CVS (along with several others). As another poster pointed out recently, it's been a long time since 2.5.6 was released (Jan 28 2003). Many recent replies to questions posted to this list are variants of "It's already fixed in CVS". Are there any particular reasons for holding

We are using rsync to push DNS records from one machine (running rsync 2.5.6 as a client process on Debian woody) to a collocation server ( running rsync 2.5.6 as a daemon on RedHat 7.3). To test this process we are using a script that pushes one file from the Debian box to the collocation server. It appears that a file transfers, but upon checking there is no file transfer and an error in the

The changes made to 2.6.0pre1 have been pretty minor so far, so I had been debating whether we needed a pre2 release or not. I finally decided to go ahead and release what little there is, just to give folks a final opportunity to double check the final release: http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz http://samba.org/ftp/rsync/preview/rsync-2.6.0pre2.tar.gz.sig

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

Hi, I am running rsync version 2.5.7 (stock distro on redhat linux, ES and 9) to rsync a directory with ~300k files in it from a machine on a 10Mbit internet tap to a machine with a 100Mbit internet tap. The problem is that I am only getting about 500Kbps during the transfer. I have tested link speed by scping a file between the two systems, performance was approximately 7.5Mbit/sec. Ping time

> On Wed, Sep 03, 2003 at 03:49:12PM -0400, Matt Miller wrote: >> I have seen this error in many postings, but the solutions seem not to >> apply in this case. This error happens during a small file transfer >> (gif image) and after 75% of a 165G rsync job (the building file list >> portion is complete.) Most solutions I saw were related to not having >>

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

currently (2.5.6) it seems to be silent and I cannot find a way to make it audible/verbose... is this possible? should it be? feature request? -Scott

I've added the: /etc/services /etc/inetd entries as well as /etc/rsync.conf with the contents: [io] path = //Volumes/Mac_OS_X/Library/WebServer/iolanguage.com/Io comment = iolanguage source code But I get this error: % rsync -rvR --progress localhost:/ . localhost.dekorte.com: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error:

A recent posting here got me thinking about having the --progress output tell the user about how many files were left to go in the transfer. I submit the attached patch which outputs an extra suffix onto the progress line at the end of each file's transfer (so it only appears once per file, not on every status update). The output would look like this: [...] flist.c 35671 100%