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.
Later,
David S. Miller
davem@redhat.com
-
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/
This archive was generated by hypermail 2b29 : Fri Jun 15 2001 - 21:00:15 EST