From: Russell King <rmk@arm.linux.org.uk>
To: kuznet@ms2.inr.ac.ru
Cc: Eugene Crosser <crosser@average.ORG>, linux-kernel@vger.kernel.org
Subject: Re: rsync over ssh on 2.4.2 to 2.2.18
Date: Mon, 19 Mar 2001 07:37:03 +0000 [thread overview]
Message-ID: <20010319073703.B16622@flint.arm.linux.org.uk> (raw)
In-Reply-To: <97hbjr$mbp$1@pccross.average.org> <200102282020.XAA05430@ms2.inr.ac.ru>
In-Reply-To: <200102282020.XAA05430@ms2.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Wed, Feb 28, 2001 at 11:20:22PM +0300
On Wed, Feb 28, 2001 at 11:20:22PM +0300, kuznet@ms2.inr.ac.ru wrote:
> 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.
Well, since I moved the rsync to 5pm, and then back to 9pm, I haven't
seen this problem - everything is again working as expected (touch wood)
with 2.2.15pre13 and 2.4.0.
This is odd, since it wasn't a one-off problem, but something that happened
each and every day of a particular week. Anyway, if it starts happening
again, I'll get a tcpdump of the session.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-03-19 8:07 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
2001-03-19 7:37 ` Russell King [this message]
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=20010319073703.B16622@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=crosser@average.ORG \
--cc=kuznet@ms2.inr.ac.ru \
--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).