Logs infos are normaly sent via syslog daemon, when rsync run in daemon rsync --rsync-path='/usr/bin/rsync --log-file=$HOME/charlotterousevarealtor.com' -t. If you want to log someting when using rsync over ssh, you have to put rsync -- rsync-path='/usr/bin/rsync --log-file=$HOME/charlotterousevarealtor.com' -t. The default behavior of rsync is to only produce output in the event of an error. rsync > /var/log/charlotterousevarealtor.com 2>&1 and inspect that file to see if the most recent.

Try your command without the --log-format option, and read the manual page for If you want to see the time for every file on the rsync client, you need to use. How do I track the progress of this cron job while rsync syncs in the with the verbose option, and redirect its output to a log that you can check. This adds to the log-file, so you can find out whether anything at all has been rsync -avr ORIG DEST --stats | grep "Number of created files".

rsync -av --rsync-path="rsync --log-file=/tmp/rlog" src/ dest/ Does anyone know how to add a log file to an rsync command? Any help would. Finally, I found a hint that the behavior of rsync described above may be a feature , not a bug: The current code logs the same way for a --log-file. rsync --log-file=/tmp/charlotterousevarealtor.com src dst In the case where rsync is copying a lot of large files slowly, I monitor that directory using watch. The original Rsync technical report and Andrew Tridgell's Phd thesis (pdf) theoretical mathematics and some of the mechanics of the rsync algorithm. From this point onward the client-server relationship is relevant only with regards to error and log message delivery. Each file will be checked to see if it can be skipped.