Hi, I have a setup where I wish to transfer around 100 files from embedded device to a connected PC. The embedded system at anytime contains 20MB free RAM. However, on running rsync periodically (20s interval), OUT OF MEMORY error results after few minutes, say 30 minutes killing this application and other application softwares running on the embedded device. rsync version is 2.6.9 and rsync command is: rsync -trze DATA/* test@a.b.c.d:/home/test/DATA Any help on what's wrong with this? Regards, Preeti -------------- next part -------------- HTML attachment scrubbed and removed
Hi, I have a setup where I wish to transfer around 100 files from embedded device to a connected PC. The embedded system at anytime contains 20MB free RAM. However, on running rsync periodically (20s interval), OUT OF MEMORY error results after few minutes, say 30 minutes killing this application and other application softwares running on the embedded device. rsync version is 2.6.9 and rsync command is: rsync -trze rsh DATA/* test@a.b.c.d:/home/test/DATA Any help on what's wrong with this? Regards, Preeti -------------- next part -------------- HTML attachment scrubbed and removed
On 5/22/07, Preeti Joshi <preetijoshi79@gmail.com> wrote:> rsync -trze DATA/* test@a.b.c.d:/home/test/DATA > > Any help on what's wrong with this?I see one thing that looks wrong, but I don't know if it is causing the out of memory. You have an -e option, which requires an argument: the name of the desired remote shell. Thus, rsync interprets the next thing on the command line (i.e., the first filename matched by DATA/*) as the remote shell and tries to execute it. I'm guessing you want to use the default remote shell (usually ssh), in which case you don't need -e at all; try removing it. Matt
On 5/23/07, Preeti Joshi <preetijoshi79@gmail.com> wrote:> I had seen the missing argument.. and posted the query again with correct > command that I am using, i.e. > rsync -trze rsh DATA/* test@a.b.c.d:/home/test/DATAI didn't notice the difference between the two messages, so I assumed they were the same and answered the first one. In the future, if you make a mistake in a message, please reply to it and just state the correction. The next thing I would check is whether rsync processes are accumulating because a new rsync is started before the previous one is finished. If that is the problem, follow the suggestions in this message to fix it: http://lists.samba.org/archive/rsync/2007-January/017133.html Matt
Matt McCutchen
2007-May-28 13:36 UTC
Fwd: problem syncing files from embedded device to PC
---------- Forwarded message ---------- From: Preeti Joshi <preetijoshi79@gmail.com> Date: May 28, 2007 5:02 AM Subject: Re: problem syncing files from embedded device to PC To: Matt McCutchen <hashproduct+rsync@gmail.com> Hi, I read the link you had mailed. I'll clarify here that I have a C application through which I invoke rsync with 'system ()' system call. Also , I have 3 threads trying to copy same source files to 3 destinations. I make sure by using threads and mutex locks that only 1 thread is created for one destination. However, 3 threads can run in parallel. Is it possible for this parallel execution of rsync to lead to OUT OF MEMORY problem even though I have such small-sized files total files being < 100 in number ! I don't think so because in few embedded systems that I have, there are only 5-6 files of few kilo bytes and still rsync leads to OUT OF MEMORY problem even with single destination. In fact I invoke rsync for destinations that are reachable by 'ping' beforehand. In case of single reachable destination too, this problem occurs within few minutes! Thus, I mostly have situations where only one instance of rsync is running! I hope rsync is not meant only for HUGE-RAM-HUGE-HARD-DISK-MILLION-FILES scenarios!!! Preeti On 5/28/07, Matt McCutchen < hashproduct+rsync@gmail.com> wrote:> On 5/23/07, Preeti Joshi < preetijoshi79@gmail.com> wrote: > > I had seen the missing argument.. and posted the query again with correct > > command that I am using, i.e. > > rsync -trze rsh DATA/* test@a.b.c.d:/home/test/DATA > > I didn't notice the difference between the two messages, so I assumed > they were the same and answered the first one. In the future, if you > make a mistake in a message, please reply to it and just state the > correction. > > The next thing I would check is whether rsync processes are > accumulating because a new rsync is started before the previous one is > finished. If that is the problem, follow the suggestions in this > message to fix it: > > http://lists.samba.org/archive/rsync/2007-January/017133.html > > Matt >