similar to: malloc errors? out of memory with many files on HP-UX

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

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 of cygwin & rsync, I recently attempted to get cygwin and rsync working to solve a backup/mirroring need in my computer life. Well, as you might guess, I ran into a little but of trouble. Strangely enough, rsync seemed to be regularly hanging when I attempted to do a "get" (sycronize a remote to a local dir). Well, considering I want to automate this, that was not going

We are using rsync to backup files from a bunch of computers to a central server using rsync in --daemon mode. I've got a problem and are looking for suggestions. I'm not a newbie to rsync and have checked the archives without getting any useable conclusions. Our old server works great - a redhat 7.2 / 2.4.18 machine. But it's getting full and there's no more updates for

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): -------------------------

Dear R Users, I have 120 objects stored in R's memory and I want to pass the names of these many objects to be held as just one single object. The naming convention is month, year in sequence for all months between January 1986 to December 1995 (e.g. Jan86, Feb86, Mar86... through to Dec95). I hope to pass all these names (and their data I guess) to an object called file_list, however,

The attached script file gives all the relevant details - I hope - please ask if you need any more information. /Sam Sam Sexton <mailto:sam.sexton@reuters.com> Reuters Coventry Automated Dealing Technologies Phone: +44 24 7625 6562 Fax: +44 24 7655 5203 -------------------------------------------------------------- -- Visit our Internet site at

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 J.W. et al, Kevin Everets was kind enough to inform me about some strange behavior in his backup script, which seems to be the result of --link-dest behaving unexpectedly in the case where target/ is already populated with older versions of the same file. Here's the situation: We want to do: $ rsync -a --link-dest=../backup.1 source/ backup.0/ There is a file present under all three

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,

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

Is it normal for rsync 2.5.5 to keep locking up on large HP/UX 11.0 files? I am not talking about a delay here, but locking up and never returning w/error. Anybody have any suggestions? Aharon -- Sr Unix Administrator Tampa, Florida Websites: http://www.tamparacing.com http://www.tampaforums.com http://www.ls6.com http://www.lastgen.com http://www.xmbforum.com

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