linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: crosser@average.ORG (Eugene Crosser)
Cc: linux-kernel@vger.kernel.org
Subject: Re: rsync over ssh on 2.4.2 to 2.2.18
Date: Wed, 28 Feb 2001 23:20:22 +0300 (MSK)	[thread overview]
Message-ID: <200102282020.XAA05430@ms2.inr.ac.ru> (raw)
In-Reply-To: <97hbjr$mbp$1@pccross.average.org> from "Eugene Crosser" at Feb 28, 1 02:15:00 am

Hello!

> I've seen hanging rsync over ssh more than once, while sending much data
> from an x86 running Linux (late 2.3.x) to Sparc/Solaris2.5.1

I remember this your report. However, recent news force to suspect
that the reason was in Solaris yet. Actually, if you send tcpdump of
failed session, this question can be answered.


Also REMEMBER!

rsync has __no__ chances to work, if one of sides is Linux-2.2 before 2.2.17
or Solaris of today (sunos-2.5.1 is enough old, probably, it still was right
unlike subsequent kernels). These stacks have conciding set of fatal bugs,
which prevent transmits with closed window.

To use rsync it is necessary to upgrade to >=2.2.17.

Alexey

  reply	other threads:[~2001-02-28 20:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 10:02 rsync over ssh on 2.4.2 to 2.2.18 Russell King
2001-02-27 10:18 ` Rasmus Andersen
2001-02-27 10:58   ` bert hubert
2001-02-27 10:49 ` David S. Miller
2001-02-27 19:46   ` Russell King
2001-02-27 13:18 ` Anton Blanchard
2001-02-27 16:48   ` Russell King
2001-02-27 20:35 ` kuznet
2001-02-27 20:43   ` Russell King
2001-02-28 20:27     ` kuznet
2001-02-27 23:01 ` Eugene Crosser
2001-02-28 20:20   ` kuznet [this message]
2001-03-19  7:37     ` Russell King
2001-03-19 18:56       ` kuznet
2001-03-21 21:54         ` Rusty Russell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200102282020.XAA05430@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=crosser@average.ORG \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).