From f97c2d4a9b78d6d93ef8cf3a5fa7d0a4b3cd4e33 Mon Sep 17 00:00:00 2001 From: Wayne Davison Date: Fri, 13 Oct 2006 01:37:44 +0000 Subject: [PATCH] - Clarified the "dont compress" option. - Cleaned up some trailing whitespace. --- rsyncd.conf.yo | 51 ++++++++++++++++++++++++++------------------------ 1 file changed, 27 insertions(+), 24 deletions(-) diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo index 37d7ccd5..4c713a3c 100644 --- a/rsyncd.conf.yo +++ b/rsyncd.conf.yo @@ -8,27 +8,27 @@ rsyncd.conf manpagedescription() The rsyncd.conf file is the runtime configuration file for rsync when -run as an rsync daemon. +run as an rsync daemon. The rsyncd.conf file controls authentication, access, logging and available modules. manpagesection(FILE FORMAT) -The file consists of modules and parameters. A module begins with the +The file consists of modules and parameters. A module begins with the name of the module in square brackets and continues until the next module begins. Modules contain parameters of the form 'name = value'. The file is line-based -- that is, each newline-terminated line represents either a comment, a module name or a parameter. -Only the first equals sign in a parameter is significant. Whitespace before +Only the first equals sign in a parameter is significant. Whitespace before or after the first equals sign is discarded. Leading, trailing and internal whitespace in module and parameter names is irrelevant. Leading and trailing whitespace in a parameter value is discarded. Internal whitespace within a parameter value is retained verbatim. -Any line beginning with a hash (#) is ignored, as are lines containing +Any line beginning with a hash (#) is ignored, as are lines containing only whitespace. Any line ending in a \ is "continued" on the next line in the @@ -37,12 +37,12 @@ customary UNIX fashion. The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 0/1 or true/false. Case is not significant in boolean values, but is preserved -in string values. +in string values. manpagesection(LAUNCHING THE RSYNC DAEMON) The rsync daemon is launched by specifying the bf(--daemon) option to -rsync. +rsync. The daemon must run with root privileges if you wish to use chroot, to bind to a port numbered under 1024 (as is the default 873), or to set @@ -58,7 +58,7 @@ When run via inetd you should add a line like this to /etc/services: verb( rsync 873/tcp) and a single line something like this to /etc/inetd.conf: - + verb( rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon) Replace "/usr/bin/rsync" with the path to where you have rsync installed on @@ -67,12 +67,12 @@ reread its config file. Note that you should bf(not) send the rsync daemon a HUP signal to force it to reread the tt(rsyncd.conf) file. The file is re-read on each client -connection. +connection. manpagesection(GLOBAL OPTIONS) The first parameters in the file (before a [module] header) are the -global parameters. +global parameters. You may also include any module parameters in the global part of the config file in which case the supplied value will override the @@ -126,7 +126,7 @@ for each module in tt(rsyncd.conf). dit(bf(use chroot)) If "use chroot" is true, the rsync daemon will chroot to the "path" before starting the file transfer with the client. This has the advantage of extra protection against possible implementation security -holes, but it has the disadvantages of requiring super-user privileges, +holes, but it has the disadvantages of requiring super-user privileges, of not being able to follow symbolic links that are either absolute or outside of the new root path, and of complicating the preservation of usernames and groups (see below). When "use chroot" is false, for security reasons, @@ -195,7 +195,7 @@ which allows the client to request one level of verbosity. dit(bf(lock file)) The "lock file" option specifies the file to use to support the "max connections" option. The rsync daemon uses record locking on this file to ensure that the max connections limit is not -exceeded for the modules sharing the lock file. +exceeded for the modules sharing the lock file. The default is tt(/var/run/rsyncd.lock). dit(bf(read only)) The "read only" option determines whether clients @@ -247,7 +247,7 @@ Because this exclude list is not passed to the client it only applies on the daemon: that is, it excludes files received by a client when receiving from a daemon and files deleted on a daemon when sending to a daemon, but it doesn't exclude files from being deleted on a client when receiving -from a daemon. +from a daemon. dit(bf(exclude from)) The "exclude from" option specifies a filename on the daemon that contains exclude patterns, one per line. @@ -313,13 +313,13 @@ username:password pairs separated by a single colon. Any line starting with a hash (#) is considered a comment and is skipped. The passwords can contain any characters but be warned that many operating systems limit the length of passwords that can be typed at the client end, so -you may find that passwords longer than 8 characters don't work. +you may find that passwords longer than 8 characters don't work. There is no default for the "secrets file" option, you must choose a name (such as tt(/etc/rsyncd.secrets)). The file must normally not be readable by "other"; see "strict modes". -dit(bf(strict modes)) The "strict modes" option determines whether or not +dit(bf(strict modes)) The "strict modes" option determines whether or not the permissions on the secrets file will be checked. If "strict modes" is true, then the secrets file must not be readable by any user ID other than the one that the rsync daemon is running under. If "strict modes" is @@ -364,7 +364,7 @@ You can also combine "hosts allow" with a separate "hosts deny" option. If both options are specified then the "hosts allow" option s checked first and a match results in the client being able to connect. The "hosts deny" option is then checked and a match means -that the host is rejected. If the host does not match either the +that the host is rejected. If the host does not match either the "hosts allow" or the "hosts deny" patterns then it is allowed to connect. @@ -383,14 +383,14 @@ phase of the transfer. Normally rsync skips the bf(--delete) step if any I/O errors have occurred in order to prevent disastrous deletion due to a temporary resource shortage or other I/O error. In some cases this test is counter productive so you can use this option to turn off this -behavior. +behavior. dit(bf(ignore nonreadable)) This tells the rsync daemon to completely ignore files that are not readable by the user. This is useful for public archives that may have some non-readable files among the directories, and the sysadmin doesn't want those files to be seen at all. -dit(bf(transfer logging)) The "transfer logging" option enables per-file +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. The daemon always logs the transfer at the end, so if a transfer is aborted, no mention will be made in the log file. @@ -414,7 +414,7 @@ The single-character escapes that are understood are as follows: quote(itemization( it() %a the remote IP address - it() %b the number of bytes actually transferred + it() %b the number of bytes actually transferred it() %B the permission bits of the file (e.g. rwxrwxrwt) it() %c the checksum bytes received for this file (only when sending) it() %f the filename (long form on sender; no trailing "/") @@ -466,15 +466,18 @@ without the former, instead refuse "delete-*" -- that refuses all the delete modes without affecting bf(--remove-sent-files). When an option is refused, the daemon prints an error message and exits. -To prevent all compression, you can use "dont compress = *" (see below) +To prevent all compression when serving files, +you can use "dont compress = *" (see below) instead of "refuse options = compress" to avoid returning an error to a client that requests compression. dit(bf(dont compress)) The "dont compress" option allows you to select filenames based on wildcard patterns that should not be compressed -during transfer. Compression is expensive in terms of CPU usage so it +when pulling files from the daemon (no analogous option exists to +govern the pushing of files to a daemon). +Compression is expensive in terms of CPU usage, so it is usually good to not try to compress files that won't compress well, -such as already compressed files. +such as already compressed files. The "dont compress" option takes a space-separated list of case-insensitive wildcard patterns. Any source filename matching one @@ -565,7 +568,7 @@ pid file = /var/run/rsyncd.pid [rsyncftp] path = /var/ftp/pub/rsync comment = rsync ftp area (approx 6 MB) - + [sambawww] path = /public_html/samba comment = Samba WWW pages (approx 240 MB) @@ -623,7 +626,7 @@ manpagesection(THANKS) Thanks to Warren Stanley for his original idea and patch for the rsync daemon. Thanks to Karsten Thygesen for his many suggestions and -documentation! +documentation! manpageauthor() @@ -631,4 +634,4 @@ rsync was written by Andrew Tridgell and Paul Mackerras. Many people have later contributed to it. Mailing lists for support and development are available at -url(http://lists.samba.org)(lists.samba.org) +url(http://lists.samba.org)(lists.samba.org) -- 2.34.1