I’ve acquired a few more Linux servers recently with Debian Squeeze installed (version 6.0.6 according to #cat \/etc\/debian_version).<\/p>\n
Installing Rsync is easy:<\/p>\n
[bash]
\napt-get install rsync
\n[\/bash]<\/p>\n
The tricks are in getting the config files done, actually running the service, connecting, etc.<\/p>\n
The default config file is in \/etc\/default\/rsync\u00a0 which sets up how rsync will run.<\/p>\n
The default settings file is expected as \/etc\/rsync.conf\u00a0 which I change to set to \/etc\/rsyncd\/rsyncd.conf\u00a0\u00a0 just so I am clear which config is ‘mine’ to work on.\u00a0 The actual change in the \/etc\/default\/rsync file is shown here with the RSYNC_CONFIG_FILE line enabled (removed the # at the start) and with the path setting as described.<\/p>\n
[text]
\n# which file should be used as the configuration file for rsync.
\n# This file is used instead of the default \/etc\/rsyncd.conf
\n# Warning: This option has no effect if the daemon is accessed
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 using a remote shell. When using a different file for
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 rsync you might want to symlink \/etc\/rsyncd.conf to
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 that file.
\nRSYNC_CONFIG_FILE=\/etc\/rsyncd\/rsyncd.conf<\/p>\n
[\/text]<\/p>\n
The other important bit is the Rsync is not enabled by default and is therefore not going to run or be running!\u00a0 In the same \/etc\/default\/rsync file edit the RSYNC_ENABLE option to change false to true<\/p>\n
[text]
\n# start rsync in daemon mode from init.d script?
\n#\u00a0 only allowed values are "true", "false", and "inetd"
\n#\u00a0 Use "inetd" if you want to start the rsyncd from inetd,
\n#\u00a0 all this does is prevent the init.d script from printing a message
\n#\u00a0 about not starting rsyncd (you still need to modify inetd’s config yourself).
\nRSYNC_ENABLE=true
\n#
\n#
\n[\/text]
\n[bash]
\n#service rsync restart
\n[\/bash]<\/p>\n
I used the restart command even though I knew that it was not running (yet) as I can reuse the command via Ctrl-R when I do more edits to the config settings<\/p>\n
[bash]
\n\/etc\/default# service rsync restart
\nRestarting rsync daemon: rsyncrsync daemon not running, attempting to start. … (warning).
\nmissing or empty config file \/etc\/rsyncd\/rsyncd.conf … failed!
\nfailed!
\n\/etc\/default#
\n[\/bash]<\/p>\n
And as expected there is a warning that it was not running to be able to stop it, and then the start action fails as there is no config file, as yet.<\/p>\n
So that is all good.<\/p>\n
Next create the appropriate config file. Easiest to start with the example conf file from the default install<\/p>\n
[bash]
\n\/etc\/rsyncd\/# cp \/usr\/share\/doc\/rsync\/examples\/rsyncd.conf .
\n[\/bash]<\/p>\n
Then edit it…<\/p>\n
[text]
\n# sample rsyncd.conf configuration file
\n# GLOBAL OPTIONS
\n#motd file=\/etc\/motd
\nlog file=\/var\/log\/rsyncd
\n# for pid file, do not use \/var\/run\/rsync.pid if
\n# you are going to run rsync out of the init.d script.
\n# pid file=\/var\/run\/rsyncd.pid
\n#syslog facility=daemon
\n#socket options=
\n[\/text]<\/p>\n
The sections in the config file are based on the sample config file and in the top Global Options I only check that the log file path is correct and enabled<\/p>\n
For each backup set that is going to be inbound to this server I add a new section to the config file:<\/p>\n
[text]
\n# MODULE OPTIONS<\/p>\n
[ftp]
\n comment = public archive <– a clever comment
\n path = \/var\/www\/pub <– set the path
\n \u00a0\u00a0\u00a0\u00a0\u00a0 use chroot = yes
\n#\u00a0\u00a0\u00a0\u00a0\u00a0 max connections=10 <– do not set it to 1
\n lock file = \/var\/lock\/rsyncd
\n# the default for read only is yes…
\n read only = yes <– change this to no so source files can be written
\n list = yes
\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0uid = nobody <– the username for the newly uploaded files
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 gid = nogroup <– the group for the files
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 exclude =
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 exclude from =
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 include =
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 include from =
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 auth users = <– comma space delimited list of names that appear in the secrets file
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 secrets file =\/etc\/rsyncd.secrets <– a text file with a username:password
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 strict modes = yes
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hosts allow = <– ip address for the source system
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hosts deny =
\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0ignore errors = no
\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0ignore nonreadable = yes
\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0transfer logging = no
\n#\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 log format = %t: host %h (%a) %o %f (%l bytes). Total %b bytes.
\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0timeout = 600
\n refuse options = checksum dry-run
\n \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz
\n[\/text]<\/p>\n
and after each update to the config file restart the service to load the new config and confirm that Rsync will run with it.<\/p>\n
[bash]
\n\/etc\/default# service rsync restart
\n[\/bash]<\/p>\n
I’ve not looked at SSH \/ SSL type connections for Rsync\u00a0in this.\u00a0The main thing was to get Rsync setup as a server and control the inbound traffic based on accounts, servers, and ip restrictions.<\/p>\n
Another post will update SSH configuration.<\/p>\n","protected":false},"excerpt":{"rendered":"
I’ve acquired a few more Linux servers recently with Debian Squeeze installed (version 6.0.6 according to #cat \/etc\/debian_version). Installing Rsync is easy: [bash] apt-get install rsync [\/bash] The tricks are in getting the config files done, actually running the service, connecting, etc. The default config file is in \/etc\/default\/rsync\u00a0 which sets up how rsync will […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,13,34],"tags":[],"class_list":["post-830","post","type-post","status-publish","format-standard","hentry","category-linux-servers-and-software","category-rsync","category-rsync-windows-servers"],"_links":{"self":[{"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/posts\/830","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/comments?post=830"}],"version-history":[{"count":0,"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/posts\/830\/revisions"}],"wp:attachment":[{"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/media?parent=830"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/categories?post=830"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/howden.net.au\/thowden\/wp-json\/wp\/v2\/tags?post=830"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}