* David S. Miller (davem@redhat.com) wrote:
>=20
> Russell King writes:
> > At the time I suggested it was because of a missing wakeup in 2.4.2 ke=
rnels,
> > but I was shouted down for using 2.2.15pre13. Since then I've seen th=
ese
> > reports appear on lkml several times, each time without a solution nor
> > explaination.
> >=20
> > Oh, and yes, we're still using the same setup here at work, and its ru=
nning
> > fine now - no rsync lockups. I'm not sure why that is. ;(
>=20
> 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.
>=20
> 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
--s8iJYNYVA1fg3NyN
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7JjCtrzgMPqB3kigRAkllAJ9WMEGs0flGG5qVr9DkF8GT6KQLuACfQBuM
mdZ/J6LqqLcpWHIIvcrhZQo=
=LsMX
-----END PGP SIGNATURE-----
--s8iJYNYVA1fg3NyN--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/