similar to: Creating a list of combinations

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

Greetings. In testing an rsync backup script I'd created, I made a mistake and aborted the running script with a ctrl-C keyboard interrupt. The command that was running at the time was as follows: ${RSYNC_CMD} -aNHAXx --protect-args --fileflags --force-change --rsync-path="/usr/local/bin/rsync" <username>@<my.server.com>:${CPY_SRC} ${CPY_DEST} The expected data

Hello again, I encountered something amazing. First I thought there is not enough memory allowed through ulimit. ulimit is now set to (almost) 512MB but rsync still gets out fo memory at 8MB. Can anyone tell me why? That's my configuration: rsync version 2.6.2 from AIX 5.3 to SuSE Linux 9 (also has rsync 2.6.2) ulimit -a (AIX) ulimit -a AIX (source): -------------------------

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

Keir, This would also be appropriate for 3.1.0, since the /usr/lib fix makes pygrub work on ia64 Presently pygrub only looks in /efi/redhat/elilo.conf. It should check for other distributions, plus a couple fallback locations. Signed-off-by: Aron Griffis <aron@hp.com> diff -r 6d64f9eefad5 -r 67df28389f46 tools/pygrub/src/pygrub --- a/tools/pygrub/src/pygrub Wed May 02 14:50:56 2007

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

I have many files in 1 directory, file names end in .txt. Each file has 2 columns col1 col2 2 3 3 4 4 5 5 6 I want to make a list of the file names and iterate through each plotting them in a separate file $filename\.png with the png swapped for txt. So far I have this, can someone help fill in the blanks? Thank You! file_list <- list.files() ? for (file in file_list){ ?????? ? ?

Hi all, I wish to merge 24 .csv files, each having a common identifier-column ("Name") and do two things: 1. Retrieve the common one's. [Analogy: while merging 2-dataframes, similar to using: merge (.... ,by="Name", all=FALSE) ] 2. Retrieve all, i.e., the union of the rows of 24 files. [again, somthing like: merge (.... ,by="Name", all=TRUE) ] On the web,

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

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch is an update to a previous patch that I submitted. The only change from the previous patch is that the const qualifier has been added to write_batch_*() routines to improve compiler efficiency. Because the gdiff -u was done against the distribution it includes the previous patch. The functions with no parameters

Hi All I run rsync in an automated environment and it sometime will crash and leave a core dump file. from core dump, gdb shows that gdb) bt #0 add_dirs_to_tree (parent_ndx=-1, from_flist=0x56c590, dir_cnt=1) at flist.c:1422 #1 0x0000000000409eab in send_file_list (f=16, argc=-1, argv=0x56c238) at flist.c:2068 #2 0x0000000000419052 in client_run (f_in=16, f_out=16, pid=-1, argc=1,

Puppet right now requires every element of a path to have an individual file definition. This makes it had to take an arbitrary path as a parameter. You are forced to require your client to make the entire path structure for you or instead you use an exec resource and call mkdir -p. Using an exec resource does not generate an File resources so autorequire does not work. I didn''t

How do you access something you''ve passed to a partial in the locals hash? <% for file in @file_list %> <tr id="file_row_<%= file[0].id %>"> <%= render_no_layout :template => "/shared/_file", :locals => { :file => file } %> </tr> <% end %> but when rendering the shared/_file.rhtml template it complains about

G'Day, rsync 3.0 to 3.2 is giving us trouble, keeps failing at certain points, latest error is :- expand file_list pointer array to 262144 bytes, did move I see this code is in flist.c, but why are we getting this and how to avoid it ? we are syncing from svn. Cheers Gav...

Hi, I am hoping that rsync may be able to improve an existing network backup I've got: tar czf - --files-from $FILE_LIST | ssh -i $AUTH -l $USER $HOST "cat > ${DEST}/${SOURCE}_${FILE}.tgz" You can see that this backup uses tar to create a single compressed archive and store it on a remote host using ssh. It occurred to me that it might be possible to use rsync. I'm hoping

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 =

People, When I did: rsync -av /home/ /mntb5/ # about 4TB I got errors like: 'rsync [sender] expand file_list pointer array to xxx bytes, "did move"' with rsync hanging - after breakout on /home for writing I then get: "Read-only file system" So after unmounting and remounting /home I did: cd /home find /home/ -type d | sort >

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%

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

Hi, What are the limits to file size and file count when doing a rsync transfer using 2.5.6? I was trying to rsync about 500 GB of data with many files and many directories, but it has been stuck building the file list for several hours. First of all, is it possible to transfer 500 GB of data? Secondly, what would the limit for file count be when doing a rsync transfer? Any comments or help