I don't remember your original question but if I didn't suggest looking
at rrsync I should have. It comes with rsync in the contrib dir and it
knows which options to allow/deny and it can restrict the transfer to a
specific dir and read-only or write-only. Since it comes with rsync it
is kept
On 21/01/19 8:07 PM, Richard Hector via rsync wrote:
> Hi all,
>
> I see a couple of earlier threads, particularly this one:
>
> https://www.mail-archive.com/rsync@lists.samba.org/msg32328.html
>
> partly answer my question, but not fully.
>
> I also am writing a wrapper, so that I can run
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #11 from Scott Peterson ---
(In reply to Haravikk from comment #4)
SPDY has apparently evolved into QUIC. QUIC supports multiple streams, which
can be created by either end. There can be a huge number of these. It seems
like a sender
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #10 from Scott Peterson ---
(In reply to Paul Slootman from comment #9)
Multiple connections also makes sense on high bandwidth links. I’ve never been
able to rsync at wire speed on a 40G link using only one connection.
--
You are
I made a bash script doing this in parallel, checks how many rsyncs are
running and then starts another 'concurrent one'. My parallel sessions
are against different servers. I doubt if it would make any sense doing
multiple sessions between the same two hosts. My single rsync sessions
was
https://bugzilla.samba.org/show_bug.cgi?id=5124
--- Comment #9 from Paul Slootman ---
The issue when copying a large number of small files is disk IO / seeking.
Check the wait for IO values using top / whatever when doing such a transfer.
Running multiple threads in such a situation will only
