Commit a85a1514 authored by Wayne Davison's avatar Wayne Davison

- Mention that "%o" can now have the value "del."

- Updated the description of "%i" to reflect the latest functioning.
parent 5dd97ab9
...@@ -377,7 +377,7 @@ quote(itemize( ...@@ -377,7 +377,7 @@ quote(itemize(
it() %a for the remote IP address it() %a for the remote IP address
it() %l for the length of the file in bytes it() %l for the length of the file in bytes
it() %p for the process ID of this rsync session it() %p for the process ID of this rsync session
it() %o for the operation, which is either "send" or "recv" it() %o for the operation, which is "send", "recv", or "del."
it() %f for the filename (long form on server; no trailing "/") it() %f for the filename (long form on server; no trailing "/")
it() %n for the filename (short form; trailing "/" on dir) it() %n for the filename (short form; trailing "/" on dir)
it() %L either the string " -> SYMLINK" or "" if not a symlink it() %L either the string " -> SYMLINK" or "" if not a symlink
...@@ -399,23 +399,25 @@ in the rsync source code distribution in the "support" subdirectory. ...@@ -399,23 +399,25 @@ in the rsync source code distribution in the "support" subdirectory.
The %i format is a set of cryptic characters that are output as follows: 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 bf(=) is output as either a bf(<) (receive) or a bf(>) (send) if the
the item is being transferred, otherwise it is a space. This lets you item is being transferred, a bf(.) if only the attributes are being
distinguish between a file that is getting its attributes changed and a updated, or a bf(=) if the items are identical. Note that when a symlink
file whose content is being updated. Note that when a symlink or a device or a device gets its value changed, that is considered to be a transfer (as
gets its value changed, that is considered to be a transfer. 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 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. "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 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; will be output if the associated attribute for the item is being updated or
otherwise the letter will be replaced by a "." for no change, a "+" a "." for no change. Three exceptions to this are: (1) a newly created
for a new item, or a "?" if the attribute is not known (which happens when item replaces each letter with a "+", (2) an identical item replaces each
talking to an older rsync). The meanings of the attribute letters are as letter with a space, and (3) an unknown attribute replaces each letter with
follows: a "?" (this happens when talking to an older rsync).
The attribute that is associated with each letter is as follows:
quote(itemize( quote(itemize(
it() A bf(c) means the checksum of the file is different and will be it() A bf(c) means the checksum of the file is different and will be
...@@ -435,6 +437,9 @@ quote(itemize( ...@@ -435,6 +437,9 @@ quote(itemize(
the authority to set the requested group). 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 dit(bf(timeout)) The "timeout" option allows you to override the
clients choice for I/O timeout for this module. Using this option you 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 can ensure that rsync won't wait on a dead client forever. The timeout
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment