>>
to make things more clear
1.)
first transfer is done either a initial setup or with a usb hdd to get
sender and receiver in sync.
2.)
transfer does not stop because rsync had a timeout, it stops because the dsl
line is broken (which i could see at dyndns)
3)
if dsl line is stable the transf
tom raschel wrote:
> Hi,
>
> i have to tranfer large files each 5-100 GB (mo-fri) over dsl line.
> unfortunately dsl lines are often not very stable and i got a broken
> pipe error.
> (dsl lines are getting a new ip if they are broken or at least after a
> reconnect every 24 hours)
>
> i had a sc
Hi,
i have to tranfer large files each 5-100 GB (mo-fri) over dsl line.
unfortunately dsl lines are often not very stable and i got a broken pipe error.
(dsl lines are getting a new ip if they are broken or at least after a
reconnect every 24 hours)
i had a script which detect the rsync error a
https://bugzilla.samba.org/show_bug.cgi?id=5637
way...@samba.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=6636
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=4168
way...@samba.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=4870
way...@samba.org changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|
I probably won't be implementing this, but since I've thought of it,
I thought I'd share.
Give rsync an option like --resumption-file=[file]
Let's say you've done:
rsync -a --resumption-file=foo a/ b/ c/
rsync starts by putting "a/" and "b/" in foo. It then gets the
listing for a/, and repl
