mailto(rsync-bugs@samba.org)
-manpage(rsyncd.conf)(5)(28 Jul 2005)()()
+manpage(rsyncd.conf)(5)(22 Apr 2006)()()
manpagename(rsyncd.conf)(configuration file for rsync in daemon mode)
manpagesynopsis()
dit(bf(log file)) The "log file" option tells the rsync daemon to log
messages to that file rather than using syslog. This is particularly
-useful on systems (such as AIX) where syslog() doesn't work for
+useful on systems (such as AIX) where code(syslog()) doesn't work for
chrooted programs. If the daemon fails to open to specified file, it
will fall back to using syslog and output an error about the failure.
(Note that a failure to open the specified log file used to be a fatal
dit(bf(socket options)) This option can provide endless fun for people
who like to tune their systems to the utmost degree. You can set all
sorts of socket options which may make transfers faster (or
-slower!). Read the man page for the setsockopt() system call for
+slower!). Read the man page for the code(setsockopt()) system call for
details on some of the options you may be able to set. By default no
special socket options are set. These settings are superseded by the
bf(--sockopts) command-line option.
In order to preserve usernames and groupnames, rsync needs to be able to
use the standard library functions for looking up names and IDs (i.e.
-getpwuid(), getgrgid(), getpwname(), and getgrnam()). This means a
+code(getpwuid()), code(getgrgid()), code(getpwname()), and code(getgrnam())). This means a
process in the chroot namespace will need to have access to the resources
used by these library functions (traditionally /etc/passwd and
/etc/group). If these resources are not available, rsync will only be
dit(bf(incoming chmod)) This option allows you to specify a set of
comma-separated chmod strings that will affect the permissions of all
incoming files (files that are being received by the daemon). These
-changes happen last, giving this setting the final word on what the
-permissions should look like in the repository.
+changes happen after all other permission calculations, and this will
+even override destination-default and/or existing permissions when the
+client does not specify bf(--perms).
See the description of the bf(--chmod) rsync option and the bf(chmod)(1)
manpage for information on the format of this string.
comma-separated chmod strings that will affect the permissions of all
outgoing files (files that are being sent out from the daemon). These
changes happen first, making the sent permissions appear to be different
-than those stored in the filesystem itself (which, for instance, you
-could disable group write permissions on the server).
+than those stored in the filesystem itself. For instance, you could
+disable group write permissions on the server while having it appear to
+be on to the clients.
See the description of the bf(--chmod) rsync option and the bf(chmod)(1)
manpage for information on the format of this string.
connect without a password (this is called "anonymous rsync").
See also the "CONNECTING TO AN RSYNC DAEMON OVER A REMOTE SHELL
-PROGRAM" section in rsync(1) for information on how handle an
+PROGRAM" section in bf(rsync)(1) for information on how handle an
rsyncd.conf-level username that differs from the remote-shell-level
username when using a remote shell to connect to an rsync daemon.
The single-character escapes that are understood are as follows:
quote(itemize(
- it() %h for the remote host name
- it() %a for the remote IP address
- it() %l for the length of the file in bytes
- it() %p for the process ID of this rsync session
- it() %o for the operation, which is "send", "recv", or "del."
- (the latter includes the trailing period)
- it() %f for the filename (long form on sender; no trailing "/")
- it() %n for the filename (short form; trailing "/" on dir)
- it() %L either the string " -> SYMLINK", or " => HARDLINK" or an
- empty string (where bf(SYMLINK) or bf(HARDLINK) is a filename)
- it() %P for the module path
- it() %m for the module name
- it() %t for the current date time
- it() %u for the authenticated username (or the null string)
- it() %b for the number of bytes actually transferred
- it() %c when sending files this gives the number of checksum bytes
- received for this file
+ it() %a the remote IP address
+ 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 "/")
+ it() %G the gid of the file (decimal) or "DEFAULT"
+ it() %h the remote host name
it() %i an itemized list of what is being updated
+ it() %l the length of the file in bytes
+ it() %L the string " -> SYMLINK", " => HARDLINK", or "" (where bf(SYMLINK) or bf(HARDLINK) is a filename)
+ it() %m the module name
+ it() %M the last-modified time of the file
+ it() %n the filename (short form; trailing "/" on dir)
+ it() %o the operation, which is "send", "recv", or "del." (the latter includes the trailing period)
+ it() %p the process ID of this rsync session
+ it() %P the module path
+ it() %t the current date time
+ it() %u the authenticated username or an empty string
+ it() %U the uid of the file (decimal)
))
For a list of what the characters mean that are output by "%i", see the
it() bf(RSYNC_EXIT_STATUS): (post-xfer only) rsync's exit value. This will be 0 for a
successful run, a positive value for an error that rsync returned
(e.g. 23=partial xfer), or a -1 if rsync failed to exit properly.
- it() bf(RSYNC_RAW_STATUS): (post-xfer only) the raw exit value from waitpid().
+ it() bf(RSYNC_RAW_STATUS): (post-xfer only) the raw exit value from code(waitpid()).
))
Even though the commands can be associated with a particular module, they
manpagesection(VERSION)
-This man page is current for version 2.6.6 of rsync.
+This man page is current for version 2.6.8 of rsync.
manpagesection(CREDITS)
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff