Re:Rsync, GUIs, power, control, design, and decisions
by darkpuma on Tuesday July 09, 2019 @02:20PM
(#20395000)
fyi, combining something like `--out-format="file: %f %l"` with `--progress` results in reasonably parse-able progress updates.
Keep in mind however that the format of --progress has changed in the past. Depending on your version of rsync it may or may not insert thousand seperating commas into the number of bytes written, e.g. 2,384,908 vs 2384908. The former can be supressed with --no-h, an option not available on at least some older versions of rsync that default to no commas.
Re:Rsync, GUIs, power, control, design, and decisions
by klodolph on Tuesday July 09, 2019 @02:33PM
(#20395143)
> It is hard to emulate what rsync does with archive mode enabled, which speeds up transfers, so tar isn't exactly a replacement for rsync.
Archive mode is what tar does by default. It is just an alias for -rlptgoD. How does this speed up transfers? Are you thinking of something else?
It is hard to emulate what rsync does with archive mode enabled, which speeds up transfers, so tar isn't exactly a replacement for rsync.
There are better ways to show progress, for example using the flag `--info=progress2`. It doesn't behave well in automated scripts though