format is like the string bf(UXcstpoga)), where bf(U) is replaced by the
kind of update being done, bf(X) is replaced by the file-type, and the
other letters represent attributes that may be output if they are being
-updated.
+modified.
The update types that replace the bf(U) are as follows:
it() A bf(>) means that a file is being transferred to the remote host
(sent).
it() A bf(c) means that a local change/creation is occuring for the item
- (such as the creation of a directory or a symlink).
+ (such as the creation of a directory or the changing of a symlink, etc.).
it() A bf(h) means that the item is a hard-link to another item (requires
bf(--hard-links)).
- it() A bf(.) means that the item only has attributes that are being
- changed.
- it() A bf(=) means that the item is identical (this only only output for
- higher levels of verbosity).
+ it() A bf(.) means that the item is not being updated (though it might
+ have attributes that are being modified).
))
The file-types that replace the bf(X) are: bf(f) for a file, a bf(d) for a
))
One other output is possible: when deleting files, the "%i" will output
-the string "deleting" for each item that is being removed (assuming that
+the string "*deleting" for each item that is being removed (assuming that
you are talking to a recent enough rsync that it logs deletions instead of
outputting them as a verbose message).
them; or an option was specified that is supported by the client and
not by the server.
dit(bf(5)) Error starting client-server protocol
+dit(bf(6)) Daemon unable to append to log-file
dit(bf(10)) Error in socket I/O
dit(bf(11)) Error in file I/O
dit(bf(12)) Error in rsync protocol data stream
dit(bf(22)) Error allocating core memory buffers
dit(bf(23)) Partial transfer due to error
dit(bf(24)) Partial transfer due to vanished source files
+dit(bf(25)) The --max-delete limit stopped deletions
dit(bf(30)) Timeout in data send/receive
enddit()