Re: Seeing with comprehension - was [ rsync error -- "Protocol incompatibility" Why?]
Richard Owlett wrote:
> Question 1
> [...]
> Question 2.
> When it ran I happened to be sitting by the display and noticed things
> of the form:
>>
>> var/log/lightdm/x-2.log.old
>> 963 100% 2.32kB/s 0:00:00 (xfr#88022, to-chk=21/128033)
>> var/log/speech-dispatcher/
>> var/mail/
>> var/opt/
>> var/spool/
>> var/spool/mail -> ../mail
>> var/spool/anacron/
>> var/spool/anacron/cron.daily
>> 9 100% 0.02kB/s 0:00:00 (xfr#88023, to-chk=14/128033)
>
> Do the lines not followed by statistics just mean "0 length files" or
> "it's just a link"?
You mean like "var/mail/" having nothing, and
"var/spool/anacron/cron.daily" having 9 100% [...]
The former is a directory (and unchanged). The latter is a file that
(appears to have) had a 9 byte update.
>
> At the end it said:
>
>>
> * Number of files: 128,033 (reg: 88,026, dir: 7,503, link: 32,466, dev:
> 37, special: 1)*
> * Number of created files: 127,995 (reg: 88,026, dir: 7,503, link:
> 32,466)*> Number of deleted files: 0
> [...]
> * sent 2,845,135,440 bytes received 1,819,035 bytes 2,837,024.89
> bytes/sec *
>
> The high-lited lines caught my attention.
> I take the first two seem just to report that rsync is copying
> intelligently.
Yep, pretty much it's:
Line 1 -> 128,033 files on the side initiating the sync
Line 2 -> 127,995 files needed to be created / updated
> I don't understand what the third is telling me when there is a
> difference between bytes sent and received. I assume it is benign as the
> was no error reported.
IIRC it's bytes we sent to the other end, and bytes the other end sent
back to us (ACKs, other stuff). I've got a big guide on rsync around
here somewhere, will send a link if I dig it up.
--
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
Reply to: