similar to: 2 instances of rsync

Dear All, I've been using rsync since almost 1 year to synchronise 2 RHEL 3 servers. Everything has been running fine until a few weeks ago. I'm getting the following error message via crond: rsync: fork failed in do_recv: Cannot allocate memory (12) rsync error: error in IPC code (code 14) at main.c(552) Here is part of the log: 2005/12/04 03:35:54 [4345] rsync on

Hi all, I have a perl-based program that creates lists of files to copy from A to B using rsync. The program can be told, when there is more than one copy list, to call rsync however many times simultaneously. This all works just fine to a point. The problem is that even though (in my test) two rsync processes have been called (check with 'ps ax | grep rsync') and in the end

Hello everybody, I am using rsync to make an identical mirror of an existing server. It's been working fine since some time now. Now, I've just added a firewire disk to both servers and created a symlink to the mounted disk within the source and destination trees: Server P (source, rsync is running as a daemon on this server): /Images |___Project1 |___Project2

Hello everyone, Server1: Harmony Server2: Peace I've been using rsync 2.6.4 since some time now, without any problem. I "copy" files from Server2 to Server1 (making Server1 a mirror of Server2). The command line used on Server1 was: rsync -vrlpogt --delete-after Server2::Img/ /LocalImg I was copying files from Server2 (module Img) to Server1 (in /LocalImg). We had a problem

If the rsyncd.conf has a line such as: log file = /var/log/rsync/log and /var/log/rsync doesn't exist or isn't a directory (or the log file can't be opened for any other reason), then there's no warning whatsoever, as rsync forks itself into the background before checking the config, opening the log file, etc. Worse still, it gets a SIGSEGV, and dumps core. Here's a strace

Hi everyone I'm still getting strange sizes on the daemon logs. After transferring around 1.66GB over 14 hours (256kbit link) to an absolutely empty directory, I get: 2007/01/26 04:13:43 [26441] sent 57014 bytes received 44708 bytes total size 1947222268 du reports the final size of the directory on the daemon side as 1.6 G, and the "received" bytes can't be 44708?! I know

https://bugzilla.samba.org/show_bug.cgi?id=10372 Summary: rsync 3.10 error in protocol data stream while rsync 3.0.9 runs through Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

https://bugzilla.samba.org/show_bug.cgi?id=10081 Summary: Multiple rsync instances conflict Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: xaionaro at gmail.com

https://bugzilla.samba.org/show_bug.cgi?id=3271 Summary: Rsync instances stay in memory when using in daemon mode Product: rsync Version: 2.6.7 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy:

I'd like to revisit the topic of moving files from system to system using rsync. I've just updated my patch from its 2.5.0 version to 2.5.1, and I'm curious what people think about getting it integrated into rsync. The patch comes in two parts. The first eliminates a potential hang condition that can happen if the data channel from the receiver to the generator gets clogged up.

All, I have read the lists, I have read the faq - yes, rsync uses a lot of memory. That said - I need to use rsync in an environment with a lot of files, and I need to use -H and --delete options. The faq says about 100 bytes per file - at the moment I am looking at 8700000 files, which should translate to about 800MB - but it does not. In fact, running rsync not only consumes all of the ram,

I'm working on trying to get rsync 2.5.6pre1 available for people to test more widely. I'm out of time for today, and I'm stuck on a problem that some machines on build.samba.org are showing on the 'chgrp' test. I can reproduce this on my home redhat 7.3 system too. It appears to be a timing problem because when I do strace -F -f on it the problem goes away. Everything seems

I just installed 313 and ran ''rails new test'' I notice the .gitignore file has entries with ''/'' prepended. Is this correct?? -joe # See http://help.github.com/ignore-files/ for more about ignoring files. # # If you find yourself ignoring temporary files generated by your text editor # or operating system, you probably want to add a global ignore instead: #

on the client i am running the following command: rsync -Cav --exclude=templates_c --port=8738 GNE_FRAMEWORK gamespot_5 c14-gs-ww1::nfs/gamespot on the server i have the following module declaration: [nfs] path = /nfs/htdocs read only = no use chroot = no exclude = gamespot_5/promos/ gamespot_5/misc/ obviously my intent is to prevent the "promos" and "misc" subdirectories

Hi All. On Mac OS10.4, using rsync 3.0, it stops during a transfer. I mount an SMB share, and then use the line: sudo rsync -avhi --delete --stats --timeout=360 --progress --log-file=/Volumes/backup/20080429/rsynclog.txt --exclude="*:*" /Volumes/RAID_One /Volumes/backup/20080429 There's a few terabytes of data, and it never finishes a complete run. It can stop at anywhere during

Rsync version 2.6.1 has been released. It is primarily a performance release that requires less memory to run, makes fewer write calls to the socket (lowering the system CPU time), does less string copying (lowering the user CPU time), and also reduces the amount of data that is transmitted over the wire. There have also been quite a few bug fixes. See the release NEWS for the full details:

Rsync version 2.6.1 has been released. It is primarily a performance release that requires less memory to run, makes fewer write calls to the socket (lowering the system CPU time), does less string copying (lowering the user CPU time), and also reduces the amount of data that is transmitted over the wire. There have also been quite a few bug fixes. See the release NEWS for the full details:

Rsync version 3.0.9pre2 is now available for release testing. This is a bug-fix release. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full summary of the changes since 3.0.8, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.0.9pre2-NEWS The changes since 3.0.9pre1 are: - Fix a hang if a

Rsync version 3.0.9pre2 is now available for release testing. This is a bug-fix release. Please test this new release and send email to the rsync mailing list with any questions, comments, or bug reports. To see a full summary of the changes since 3.0.8, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.0.9pre2-NEWS The changes since 3.0.9pre1 are: - Fix a hang if a

I am having some problems getting rsync working. No files get copied, although the server HD light DOES come on for about a second when I run the client rsync command. The /etc/rsyncd.conf on the server: ============================== uid = root gid = root log = /var/log/rsync.log read only = no [email] # Email data files from /var/spool/mail on Proxy (192.168.0.100) path = /home/databackup/