Difference between revisions of "Rsyncd"
m |
(Added note about ftp security (the need for IP restricted locations).) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 24: | Line 24: | ||
sending incremental file list | sending incremental file list | ||
logo.gif | logo.gif | ||
| + | | ||
| + | sent 38.43K bytes received 27 bytes 76.92K bytes/sec | ||
| + | total size is 38.34K speedup is 1.00 | ||
| + | Pushes the file logo.gif to the rsyncd location SWALIM. Take note of the files listed under "sending incremental file list". Any files already present in the destination will not be listed. For example: | ||
| + | |||
| + | [libby@rain ~]$ rsync -avh logo.gif rsyncd.chg.ucsb.edu::SWALIM | ||
| + | sending incremental file list | ||
| + | logo.gif | ||
| + | | ||
sent 38.43K bytes received 27 bytes 76.92K bytes/sec | sent 38.43K bytes received 27 bytes 76.92K bytes/sec | ||
total size is 38.34K speedup is 1.00 | total size is 38.34K speedup is 1.00 | ||
| + | [libby@rain ~]$ rsync -avh logo.gif rsyncd.chg.ucsb.edu::SWALIM | ||
| + | sending incremental file list | ||
| + | | ||
| + | sent 44 bytes received 8 bytes 104.00 bytes/sec | ||
| + | total size is 38.34K speedup is 737.33 | ||
| − | + | To send an entire directory, the process is the same. Instead of listing the filename, list the directory name or the path to the directory. | |
| + | |||
| + | [libby@rain ~]$ rsync -avh foodir/ rsyncd.chg.ucsb.edu::SWALIM | ||
| + | sending incremental file list | ||
| + | ./ | ||
| + | foo.log-20150215 | ||
| + | foo.log-20150217 | ||
| + | foo.log-20150222 | ||
| + | foo.log-20150301 | ||
| + | foo.log-20150304 | ||
| + | foo.log-20150308 | ||
| + | test/ | ||
| + | test/foo.testlog | ||
| + | test/foo.testoutput-20150723_130024 | ||
| + | test/foo.sh | ||
| + | | ||
| + | sent 590.17M bytes received 608 bytes 90.80M bytes/sec | ||
| + | total size is 590.10M speedup is 1.00 | ||
==rsyncd Locations== | ==rsyncd Locations== | ||
rsyncd destination points must be requested and set up in advance. Please contact [mailto:chgadmin@geog.ucsb.edu chgadmin@geog.ucsb.edu] to request a destination point. | rsyncd destination points must be requested and set up in advance. Please contact [mailto:chgadmin@geog.ucsb.edu chgadmin@geog.ucsb.edu] to request a destination point. | ||
| + | |||
| + | If the user wants an rsync destination point that will be immediately available via ftp-out, they will need to provide an IP for security reasons. | ||
Latest revision as of 08:29, 25 July 2016
To help facilitate pushing incoming data to CHG, an rsyncd server has been set up on range. Currently, this does not so much replace the ftp-in function as supplement it, though eventually it will likely replace ftp-in.
Gettings Started
To push data to CHG servers, you will need a Unix-based command line interface equipped with the rsync command.
Windows
There are several options for Windows users who want a Unix-based command line interface. One of the most commonly used programs is Cygwin. You can find more about installing Cygwin here. Make sure to select rsync as one of the packages when you install. You may want to check for the "mirror" (or website you will download the Cygwin files from) closest to you here. Keep in mind that installing Cygwin, especially if you choose to do a full install, could take quite a while.
Another option is putty.
Mac/OS X
You should be able to use the built-in Terminal program to use rsync.
Command Line
[user@server ~]$ rsync -avh foo.txt rsyncd.chg.ucsb.edu::[rsync-destination-point]
Where "foo.txt" is the file or path to the file(s) to be rsync'd and rsyncd.chg.ucsb.edu is the rsyncd server (located on range), and the ::[rsync destination point] is the predetermined location where you want to push your data. For example:
[libby@rain ~]$ rsync -avh logo.gif rsyncd.chg.ucsb.edu::SWALIM sending incremental file list logo.gif sent 38.43K bytes received 27 bytes 76.92K bytes/sec total size is 38.34K speedup is 1.00
Pushes the file logo.gif to the rsyncd location SWALIM. Take note of the files listed under "sending incremental file list". Any files already present in the destination will not be listed. For example:
[libby@rain ~]$ rsync -avh logo.gif rsyncd.chg.ucsb.edu::SWALIM sending incremental file list logo.gif sent 38.43K bytes received 27 bytes 76.92K bytes/sec total size is 38.34K speedup is 1.00 [libby@rain ~]$ rsync -avh logo.gif rsyncd.chg.ucsb.edu::SWALIM sending incremental file list sent 44 bytes received 8 bytes 104.00 bytes/sec total size is 38.34K speedup is 737.33
To send an entire directory, the process is the same. Instead of listing the filename, list the directory name or the path to the directory.
[libby@rain ~]$ rsync -avh foodir/ rsyncd.chg.ucsb.edu::SWALIM sending incremental file list ./ foo.log-20150215 foo.log-20150217 foo.log-20150222 foo.log-20150301 foo.log-20150304 foo.log-20150308 test/ test/foo.testlog test/foo.testoutput-20150723_130024 test/foo.sh sent 590.17M bytes received 608 bytes 90.80M bytes/sec total size is 590.10M speedup is 1.00
rsyncd Locations
rsyncd destination points must be requested and set up in advance. Please contact chgadmin@geog.ucsb.edu to request a destination point.
If the user wants an rsync destination point that will be immediately available via ftp-out, they will need to provide an IP for security reasons.
