Gitiles
Code Review Sign In
gerrit.witaqua.org / external_rsync / 584ec839c0bc2fd19cf2940008c14873600dabb0
commit584ec839c0bc2fd19cf2940008c14873600dabb0[log] [tgz]
authorDylan Simon <dylan@dylex.net>Mon Mar 08 22:01:26 2010 -0500
committerLuK1337 <priv.luk@gmail.com>Wed Sep 09 19:08:43 2020 +0200
tree0cec41477641c9636723b91da4c14a146e322d9d
parente94bad1c156fc3910f24e2b3b71a81b0b0bdeb70 [diff]
Android build, static config, and changes

Works fine on emulator both for local copies and in daemon mode.  Very few changes necessary.

Change-Id: I6ef54769b00333f84eabd1306381eac80b3d5f09

proto.h update

Add LOCAL_MODULE_TAGS

Change-Id: Id972b0c0c876477cb29fcb9bb5b4a9c6be6703c0

update config.h and proto.h

Fix build with 4.3's bionic

Change-Id: I09ca525c26571d8dd492339a6763f012783531ef

Fix android compilation for 3.1.1

Change-Id: Ic8c134020beb98e1e52c4d527cbdbfe591d67262

rsync: Fix compilation for O-MR1

Change-Id: I546bbb40339cfce8fe854596fa7442fa0c08b43e

rsync: fix build after 3.1.2 rebase

Change-Id: I6fd02633db2ce15f60299174ae5b34df577195a5

revert dev_t changes

Change-Id: I947106cd86617bdc48a23a03191d491dbe4ca5ea
13 files changed
tree: 0cec41477641c9636723b91da4c14a146e322d9d
  1. .github/
  2. doc/
  3. lib/
  4. m4/
  5. packaging/
  6. popt/
  7. support/
  8. testhelp/
  9. testsuite/
  10. zlib/
  11. .cirrus.yml
  12. .gitattributes
  13. .gitignore
  14. access.c
  15. acls.c
  16. Android.mk
  17. authenticate.c
  18. backup.c
  19. batch.c
  20. byteorder.h
  21. case_N.h
  22. checksum.c
  23. chmod.c
  24. cleanup.c
  25. clientname.c
  26. clientserver.c
  27. cmdormsg
  28. compat.c
  29. config.guess
  30. config.h
  31. config.sub
  32. configure
  33. configure.ac
  34. connection.c
  35. COPYING
  36. csprotocol.txt
  37. daemon-parm.awk
  38. daemon-parm.h
  39. daemon-parm.txt
  40. default-cvsignore.h
  41. default-dont-compress.h
  42. define-from-md.awk
  43. delete.c
  44. Doxyfile
  45. errcode.h
  46. exclude.c
  47. fileio.c
  48. flist.c
  49. generator.c
  50. getfsdev.c
  51. getgroups.c
  52. git-version.h
  53. hashtable.c
  54. help-from-md.awk
  55. help-rsync.h
  56. help-rsyncd.h
  57. hlink.c
  58. ifuncs.h
  59. install-sh
  60. INSTALL.md
  61. inums.h
  62. io.c
  63. io.h
  64. itypes.h
  65. latest-year.h
  66. loadparm.c
  67. log.c
  68. main.c
  69. Makefile.in
  70. match.c
  71. maybe-make-man
  72. md2man
  73. mkgitver
  74. mkproto.awk
  75. NEWS.md
  76. options.c
  77. params.c
  78. pipe.c
  79. prepare-source
  80. prepare-source.mak
  81. progress.c
  82. proto.h
  83. README.md
  84. receiver.c
  85. rounding.c
  86. rounding.h
  87. rsync-ssl
  88. rsync-ssl.1.md
  89. rsync.1.md
  90. rsync.c
  91. rsync.h
  92. rsync3.txt
  93. rsyncd.conf.5.md
  94. rsyncsh.txt
  95. runtests.sh
  96. sender.c
  97. shconfig.in
  98. simd-checksum-x86_64.cpp
  99. socket.c
  100. stunnel-rsyncd.conf.in
  101. syscall.c
  102. t_stub.c
  103. t_unsafe.c
  104. tech_report.tex
  105. testrun.c
  106. tls.c
  107. TODO
  108. token.c
  109. trimslash.c
  110. uidlist.c
  111. usage.c
  112. util.c
  113. util2.c
  114. version.h
  115. wildtest.c
  116. wildtest.txt
  117. xattrs.c
README.md

WHAT IS RSYNC?

Rsync is a fast and extraordinarily versatile file copying tool for both remote and local files.

Rsync uses a delta-transfer algorithm which provides a very fast method for bringing remote files into sync. It does this by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand. At first glance this may seem impossible because the calculation of diffs between two files normally requires local access to both files.

A technical report describing the rsync algorithm is included with this package.

USAGE

Basically you use rsync just like scp, but rsync has many additional options. To get a complete list of supported options type:

rsync --help

See the manpage for more detailed information.

BUILDING AND INSTALLING

If you need to build rsync yourself, check out the INSTALL page for information on what libraries and packages you can use to get the maximum features in your build.

SETUP

Rsync normally uses ssh or rsh for communication with remote systems. It does not need to be setuid and requires no special privileges for installation. You must, however, have a working ssh or rsh system. Using ssh is recommended for its security features.

Alternatively, rsync can run in `daemon' mode, listening on a socket. This is generally used for public file distribution, although authentication and access control are available.

To install rsync, first run the "configure" script. This will create a Makefile and config.h appropriate for your system. Then type "make".

Note that on some systems you will have to force configure not to use gcc because gcc may not support some features (such as 64 bit file offsets) that your system may support. Set the environment variable CC to the name of your native compiler before running configure in this case.

Once built put a copy of rsync in your search path on the local and remote systems (or use "make install"). That's it!

RSYNC DAEMONS

Rsync can also talk to "rsync daemons" which can provide anonymous or authenticated rsync. See the rsyncd.conf(5) man page for details on how to setup an rsync daemon. See the rsync(1) man page for info on how to connect to an rsync daemon.

WEB SITE

For more information, visit the main rsync web site.

You'll find a FAQ list, downloads, resources, HTML versions of the manpages, etc.

MAILING LISTS

There is a mailing list for the discussion of rsync and its applications that is open to anyone to join. New releases are announced on this list, and there is also an announcement-only mailing list for those that want official announcements. See the mailing-list page for full details.

BUG REPORTS

The bug-tracking web page has full details on bug reporting.

That page contains links to the current bug list, and information on how to do a good job when reporting a bug. You might also like to try searching the Internet for the error message you've received, or looking in the mailing list archives.

To send a bug report, follow the instructions on the bug-tracking page of the web site.

Alternately, email your bug report to rsync@lists.samba.org.

GIT REPOSITORY

If you want to get the very latest version of rsync direct from the source code repository, then you will need to use git. The git repo is hosted on GitHub and on Samba's site.

See the download page for full details on all the ways to grab the source.

COPYRIGHT

Rsync was originally written by Andrew Tridgell and is currently maintained by Wayne Davison. It has been improved by many developers from around the world.

Rsync may be used, modified and redistributed only under the terms of the GNU General Public License, found in the file COPYING in this distribution, or at the Free Software Foundation.