slackbuilds/network/UDR
Andrew Clemons ab950a9ac4
network/UDR: Fix github tarball handling.
Signed-off-by: Andrew Clemons <andrew.clemons@gmail.com>

Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
2022-02-06 15:47:08 +07:00
..
README network/UDR: Updated for version 0.9.4_774f2e7. 2020-09-04 00:20:30 +07:00
UDR.SlackBuild network/UDR: Fix github tarball handling. 2022-02-06 15:47:08 +07:00
UDR.info network/UDR: Fix github tarball handling. 2022-02-06 15:47:08 +07:00
slack-desc network/UDR: Updated for version 0.9.4_774f2e7. 2020-09-04 00:20:30 +07:00

README

UDR is a wrapper around rsync that enables rsync to use UDT protocol and
thus improves throughput of large data transfers over long distances.

UDT is a UDP-based, application level protocol. It is designed to
support transferring large datasets over high speed wide area networks,
where TCP has been known to be extremely ineffective.

UDR does not change rsync, it works by creating a UDT connection and
then places the connection between the rsync client and server.

To use UDR, prefix the current rsync command used to transfer data with
'udr', for example:

udr rsync -av /home/user/dir/ user@example.com:/home/user/dir

Any rsync options can be used.

UDR must be on the client and server machines that data will be
transferred between. UDR uses ssh to do authentication and automatically
start the server-side UDR process. At least one UDP port needs to be
open between the machines.