Learn more about these different git repos.
Other Git URLs
If debugging is 0, you get no rsync output. If it's 1, you get rsync output but it's not particularly useful.
Also, we don't really want to see "too many connections" errors, since those aren't abnormal and will just result in spam from cron.
We should collect rsync output somewhere and parse it ourselves unless debugging is high enough that you really want to see it all.
The rsync output is collected, Now that --stats is in the set of defaut options, there is some really useful data we want to grep out of the logs. Pretty much everything that --stats provides, but specifically the time spent building the file list, since that's what we really want to use for advertising.
Also, we should consider passing some verbosity flag to rsync so that another utility can tail the log and get live status output. This should be controlled separately from the regular verbosity.
But how to then grep out what we might want to show in the regular output log? We probably don't want to show any of it but it might be possible to "compress" the output by removing lines whch were overwriten by \r. That might be a fun trick.
The rsync log is collected now, and useful things are grepped out of it at the end of the run. I'm going to go ahead and close this.
@tibbs changed the status to Fixed
Fixed
Login to comment on this ticket.