This is the mail archive of the
mailing list for the Cygwin project.
Re: Telnet / SSH connection timeout on LAN
- From: Warren Young <wyml at etr-usa dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 13 Jul 2015 07:10:28 -0600
- Subject: Re: Telnet / SSH connection timeout on LAN
- Authentication-results: sourceware.org; auth=none
- References: <1436142936994-119480 dot post at n5 dot nabble dot com> <7931485F-EEA3-4C1B-8B2C-E495EF5ED1A9 at etr-usa dot com> <1283519593 dot 20150709090453 at yandex dot ru> <5C24455B-3D28-4C6D-A77B-70BB5D67F0AA at etr-usa dot com> <1023815842 dot 20150711053838 at yandex dot ru>
On Jul 10, 2015, at 8:38 PM, Andrey Repin <firstname.lastname@example.org> wrote:
>> Consider all the disk I/O required. In its default mode, rsync must do a
>> full directory tree scan on the directory to be transferred, on *both* ends.
>> For each file with a different mtime or size, it must then recompute all the
>> hashes in that file, again on both sides.
> Wrong. In default mode, rsync only care about timestamp and size.
> It will not go on hashing crusade unless explicitly told to.
You misunderstood what I wrote. Given a changed mtime or file size, rsync then must re-read the file on both sides in order to generate a series of checksums on chunks of the file in order to determine which parts of the file have changed, so that it transfers only the changes. See:
If you skip this step, you must transfer the entire file contents to the other side, since a difference only in the mtime and/or file size doesnât tell you which parts of the file have changed.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple