X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/3ca8e68f58e7ffeac5b8b969ef26bffc2069f113..66203a982b3d249bafda9b9272c4c103c19e4a9b:/rsyncd.conf.yo diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo index 5634d9e7..3f6e01e4 100644 --- a/rsyncd.conf.yo +++ b/rsyncd.conf.yo @@ -1,5 +1,5 @@ mailto(rsync-bugs@samba.org) -manpage(rsyncd.conf)(5)(9 Feb 1999)()() +manpage(rsyncd.conf)(5)(12 Feb 1999)()() manpagename(rsyncd.conf)(configuration file for rsync server) manpagesynopsis() @@ -58,8 +58,9 @@ and a single line something like this to /etc/inetd.conf: quote(rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon) -You will then need to send inetd a HUP signal to tell it to reread its -config file. +Replace "/usr/bin/rsync" with the path to where you have rsync installed on +your system. You will then need to send inetd a HUP signal to tell it to +reread its config file. Note that you should not send the rsync server a HUP signal to force it to reread the tt(/etc/rsyncd.conf). The file is re-read on each client @@ -165,7 +166,12 @@ group "nobody". dit(bf(exclude)) The "exclude" option allows you to specify a space separated list of patterns to add to the exclude list. This is equivalent to the client specifying these patterns with the --exclude -option. Note that this option is not designed with strong security in +option except that the exclude list is not passed to the client and +thus only apply on the server. Only one "exclude" option may be +specified, but you can use "-" and "+" before patterns to specify +exclude/include. + +Note that this option is not designed with strong security in mind, it is quite possible that a client may find a way to bypass this exclude list. If you want to absolutely ensure that certain files cannot be accessed then use the uid/gid options in combination with @@ -174,17 +180,19 @@ file permissions. dit(bf(exclude from)) The "exclude from" option specifies a filename on the server that contains exclude patterns, one per line. This is equivalent to the client specifying the --exclude-from option with a -equivalent file. See also the note about security for the exclude -option above. +equivalent file except that the resulting exclude patterns are not +passed to the client and thus only apply on the server. See also the +note about security for the exclude option above. dit(bf(include)) The "include" option allows you to specify a space separated list of patterns which rsync should not exclude. This is equivalent to the client specifying these patterns with the --include -option. This is useful as it allows you to build up quite complex -exclude/include rules. +option. This is useful as it allows you to build up quite complex +exclude/include rules. Only one "include" option may be specified, but you +can use "+" and "-" before patterns to switch include/exclude. -See the section of exclude patterns for information on the syntax of -this option. +See the section of exclude patterns in the rsync man page for information +on the syntax of this option. dit(bf(include from)) The "include from" option specifies a filename on the server that contains include patterns, one per line. This is @@ -266,6 +274,14 @@ rejected. See the "hosts allow" option for more information. The default is no "hosts deny" option, which means all hosts can connect. +dit(bf(ignore errors)) The "ignore errors" option tells rsyncd to +ignore IO errors on the server when deciding whether to run the delete +phase of the transfer. Normally rsync skips the --delete step if any +IO errors have occurred in order to prevent disasterous deletion due +to a temporary resource shortage or other IO error. In some cases this +test is counter productive so you can use this option to turn off this +behaviour. + dit(bf(transfer logging)) The "transfer logging" option enables per-file logging of downloads and uploads in a format somewhat similar to that used by ftp daemons. If you want to customize the log formats look at