Feature request, or HowTo? State-full resume rsync transfer

2011-07-11 Thread Donald Pearson
I am looking to do state-full resume of rsync transfers. My network environment is is an unreliable and slow satellite infrastructure, and the files I need to send are approaching 10 gigs in size. In this network environment often times links cannot be maintained for more than a few minutes at a

Re: Feature request, or HowTo? State-full resume rsync transfer

2011-07-11 Thread Eberhard Moenkeberg
Hi, On Mon, 11 Jul 2011, Donald Pearson wrote: I am looking to do state-full resume of rsync transfers. My network environment is is an unreliable and slow satellite infrastructure, and the files I need to send are approaching 10 gigs in size. In this network environment often times links

Re: Feature request, or HowTo? State-full resume rsync transfer

2011-07-11 Thread Eberhard Moenkeberg
Hi once more, On Mon, 11 Jul 2011, Eberhard Moenkeberg wrote: On Mon, 11 Jul 2011, Donald Pearson wrote: I am looking to do state-full resume of rsync transfers. My network environment is is an unreliable and slow satellite infrastructure, and the files I need to send are approaching 10

Re: Feature request, or HowTo? State-full resume rsync transfer

2011-07-11 Thread Leen Besselink
On 07/11/2011 10:57 PM, Eberhard Moenkeberg wrote: Hi once more, On Mon, 11 Jul 2011, Eberhard Moenkeberg wrote: On Mon, 11 Jul 2011, Donald Pearson wrote: I am looking to do state-full resume of rsync transfers. My network environment is is an unreliable and slow satellite

Re: inefficient: --checksum calculation shouldn't be done for new files

2011-07-11 Thread Carlos Carvalho
Wayne Davison (way...@samba.org) wrote on 4 July 2011 17:10: On Sat, Jul 2, 2011 at 5:46 PM, Carlos Carvalho car...@fisica.ufpr.br wrote: When --checksum is used they're calculated in both ends to see if theĀ file should be transfered. This is of course not necessary if the fileĀ 

use-after-free in open_socket_out

2011-07-11 Thread Carlos Carvalho
Since 3.0.8 (the same in 3.1) we have this around line 300 in socket.c: break; } freeaddrinfo(res0); if (s 0) { char buf[2048]; for (res = res0, j = 0; res; res = res-ai_next, j++) { if (errnos[j] == 0) continue; if

Re: use-after-free in open_socket_out

2011-07-11 Thread Wayne Davison
res0 is freed but keeps its value so there's access to freed memory in res-ai* in the call of inet_ntop if s 0. Thanks. I've commited the fix. ..wayne.. -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options:

[SCM] The rsync repository. - branch b3.0.x updated

2011-07-11 Thread Rsync CVS commit messages
The branch, b3.0.x has been updated via 5fed6c0 Move freeaddrinfo() call after failure-reporting loop. from 30fb28c Mention the latest fixes. ;a=shortlog;h=b3.0.x - Log - commit