delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
DomainKey-Signature: | a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:content-type:mime-version:subject:from | |
:in-reply-to:date:content-transfer-encoding:message-id | |
:references:to; q=dns; s=default; b=gpjonuS3rwpyxK0n2EoKVVg9G8mF | |
FAXJYyap+Wz7hFmRd1kFZWrQI2hf41t+WXyWiIcFjqPcqfkxopYRPmYWaHUh4CAH | |
N8v+YAejJXKXCOg/9CIFB7+gA4EfFd3QyqHKZ515XGJd7mrpcnmnlBapvuxYbgLC | |
LVuT8UvRKmRaPsA= | |
DKIM-Signature: | v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id |
:list-unsubscribe:list-subscribe:list-archive:list-post | |
:list-help:sender:content-type:mime-version:subject:from | |
:in-reply-to:date:content-transfer-encoding:message-id | |
:references:to; s=default; bh=Hx6iSDeHmlo595aaNvgrjhzBNIE=; b=hI | |
dB1CuzhRLk9nC0ADZgr4r+p3wCARyz0BkKuZHcoVrphKrEkrRZTLFQayXrtjRa9b | |
tFD5Z6ThXtm3u4Oy3FVXkMdMAz+PuIR7yFGl/N3FHpNyjRqB71d8mRiE7ZZhp+8m | |
9pAwqcp5DPMfk4KgEk/EeGHrzcmbVHo4NCWggE298= | |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Authentication-Results: | sourceware.org; auth=none |
X-Virus-Found: | No |
X-Spam-SWARE-Status: | No, score=0.1 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 |
X-HELO: | etr-usa.com |
Mime-Version: | 1.0 (Mac OS X Mail 8.2 \(2102\)) |
Subject: | Re: Telnet / SSH connection timeout on LAN |
From: | Warren Young <wyml AT etr-usa DOT com> |
In-Reply-To: | <1023815842.20150711053838@yandex.ru> |
Date: | Mon, 13 Jul 2015 07:10:28 -0600 |
Message-Id: | <F96E2C14-5C27-43A0-AC16-DDF01F05BB23@etr-usa.com> |
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> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id t6DDAjxh018486 |
On Jul 10, 2015, at 8:38 PM, Andrey Repin <anrdaemon AT yandex DOT ru> 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: https://en.wikipedia.org/wiki/Rsync#Determining_which_parts_of_a_file_have_changed 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 FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |