From: Stephen Frost <sfrost@snowman.net>
To: "David S. Miller" <davem@redhat.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
Jeremy Sanders <jss@ast.cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: rsync hangs on RedHat 2.4.2 or stock 2.4.4
Date: Tue, 12 Jun 2001 11:09:33 -0400 [thread overview]
Message-ID: <20010612110933.G11136@ns> (raw)
In-Reply-To: <Pine.LNX.4.33.0106121417130.10732-100000@xpc1.ast.cam.ac.uk> <20010612154735.B17905@flint.arm.linux.org.uk> <15142.11907.782662.581523@pizda.ninka.net>
In-Reply-To: <15142.11907.782662.581523@pizda.ninka.net>; from davem@redhat.com on Tue, Jun 12, 2001 at 08:00:19AM -0700
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
* David S. Miller (davem@redhat.com) wrote:
>
> Russell King writes:
> > At the time I suggested it was because of a missing wakeup in 2.4.2 kernels,
> > but I was shouted down for using 2.2.15pre13. Since then I've seen these
> > reports appear on lkml several times, each time without a solution nor
> > explaination.
> >
> > Oh, and yes, we're still using the same setup here at work, and its running
> > fine now - no rsync lockups. I'm not sure why that is. ;(
>
> Look everyone, it was determined to be a deadlock because of some
> interaction between how rsync sets up it's communication channels
> with the ssh subprocess, readas: userland bug.
>
> I don't remember if the specific problem was in rsync itself or some
> buggy version of ssh. One can search the list archives to discover
> Alexey's full analysis of the problem. I don't have a URL handy.
I have to say I find this likely to be the case for those who are
having issues with rsync over ssh. I was recently playing with
rsync over ssh (newer openssh to older openssh) and was just using
it as a pass-through to another machine.
When I replaced ssh with rinetd, everything worked fine. I havn't
had a chance yet (though I'd like to) to try with two recent versions
of ssh but I'm curious what the result will be. It may be that the
problem has been fixed in later versions of ssh.
Stephen
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-06-12 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 13:59 rsync hangs on RedHat 2.4.2 or stock 2.4.4 Jeremy Sanders
2001-06-12 14:09 ` Rasmus Andersen
2001-06-12 14:17 ` Disconnect
2001-06-12 14:47 ` Russell King
2001-06-12 15:00 ` David S. Miller
2001-06-12 15:01 ` Jeremy Sanders
2001-06-12 15:09 ` Stephen Frost [this message]
2001-06-12 15:23 ` Disconnect
2001-06-12 20:22 ` Rasmus Andersen
2001-06-19 9:41 ` Jeremy Sanders
2001-06-21 19:38 ` Rasmus Andersen
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=20010612110933.G11136@ns \
--to=sfrost@snowman.net \
--cc=davem@redhat.com \
--cc=jss@ast.cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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