Displaying 2 results from an estimated 2 matches for "recv_rules".
Did you mean:
recv_files
2009 Aug 26
1
rsync proxy
...e", however I am trying to make it so that on the
'client' end, I can have my code call rsync, instead of the other way
around.
When I call --server on the 'client' end, rsync seems to handshake OK,
but I get buffer overflow errors:
<snip>
ERROR: buffer overflow in recv_rules [sender]
rsync error: error allocating core memory buffers (code 22) at /
SourceCache/rsync/rsync-35.2/rsync/util.c(121) [sender=2.6.9]
</snip>
The above is sent from the 'server' to the 'client'.
Before I go delving in to the code, is --server supposed to be used in
this...
2011 Oct 28
3
Strange bug (buffer overflow) happening only under cron
...111028133407.4BC171BF226 at mypera.local>
Date: Fri, 28 Oct 2011 15:34:01 +0200 (CEST)
Status: RO
cp: ./Dropbox/HostMonsterPage/doc/ampliacion.pdf: No such file or directory
cp: ./Dropbox/HostMonsterPage/doc/metodos.pdf: No such file or directory
building file list ... ERROR: buffer overflow in recv_rules [Receiver]
rsync error: error allocating core memory buffers (code 22) at util.c(123) [Receiver=3.0.9]
rsync: connection unexpectedly closed (157 bytes received so far) [sender]
rsync error: error allocating core memory buffers (code 22) at io.c(605) [sender=3.0.9]
I am attaching a -avvvv output a...