mailto(rsync-bugs@samba.org)
-manpage(rsyncd.conf)(5)(30 Sep 2004)()()
+manpage(rsyncd.conf)(5)(22 Feb 2005)()()
manpagename(rsyncd.conf)(configuration file for rsync server)
manpagesynopsis()
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 either "send" or "recv"
- it() %f for the filename (long form on server; no trailing "/")
+ it() %o for the operation, which is "send", "recv", or "del."
+ 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 "" if not a symlink
it() %P for the module path
it() %i an itemized list of what is being updated
))
-The default log format is "%o %h [%a] %m (%u) %l %f%L", and a "%t [%p] "
+The default log format is "%o %h [%a] %m (%u) %f %l", and a "%t [%p] "
is always prefixed when using the "log file" option.
A perl script called rsyncstats to summarize this format is included
The %i format is a set of cryptic characters that are output as follows:
-quote(tt( *Xcstpog ITEM_NAME))
+quote(tt( =Xcstpog ITEM_NAME))
-The bf(*) is either bf(<) (receive), bf(>) (send), or bf(*) (--dry-run) if
-the item is being transferred, otherwise it is a space. This lets you
-distinguish between a file that is getting its attributes changed and a
-file whose content is being updated. Note that when a symlink or a device
-gets its value changed, that is considered to be a transfer.
+The bf(=) is output as either a bf(<) (receive) or a bf(>) (send) if the
+item is being transferred, a bf(.) if only the attributes are being
+updated, or a bf(=) if the items are identical. Note that when a symlink
+or a device gets its value changed, that is considered to be a transfer (as
+opposed to a change in permissions or ownership).
The bf(X) will be replaced by one of the following: an "f" for a file, a
"d" for a dir, an "L" for a symlink, or a "D" for a device.
The rest of the letters in the string above are the actual letters that
-will be output if the associated attribute for the item is being updated;
-otherwise the letter will be replaced by a "." for no change, a "+"
-for a new item, or a "?" if the attribute is not known (which happens when
-talking to an older rsync). The meanings of the attribute letters are as
-follows:
+will be output if the associated attribute for the item is being updated or
+a "." for no change. Three exceptions to this are: (1) a newly created
+item replaces each letter with a "+", (2) an identical item replaces each
+letter with a space, and (3) an unknown attribute replaces each letter with
+a "?" (this happens when talking to an older rsync).
+
+The attribute that is associated with each letter is as follows:
quote(itemize(
it() A bf(c) means the checksum of the file is different and will be
the authority to set the requested group).
))
+One other output is possible: when deleting files, each deleted file will
+be logged with the "%i" taking on a value of "deleting".
+
dit(bf(timeout)) The "timeout" option allows you to override the
clients choice for I/O timeout for this module. Using this option you
can ensure that rsync won't wait on a dead client forever. The timeout
The reason the above refuses all delete options is that the options imply
bf(--delete), and implied options are refused just like explicit options.
+As an additional safety feature, the refusal of "delete" also refuses
+bf(remove-sent-files) when the daemon is the sender; if you want the latter
+without the former, instead refuse "delete-*" -- that refuses all the
+delete modes without affecting bf(--remove-sent-files).
When an option is refused, the server prints an error message and exits.
To prevent all compression, you can use "dont compress = *" (see below)
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff