David, What does "netstat -t" show at both ends when this happens? The reason I keep coming back to this is that this is the most reliable way of telling whether the problem is in rsync or the kernel. It also tells us which end is clagged up. If one end shows that it has data in the sendq and it is not moving (see if it changes in size) and the other end shows no data in the recvq then you know that it must be a kernel bug. We have encountered that a few of times here with a network card that drops a high percentage of packets. (dropping packets should not causes this with tcp, but it seems to trigger a Linux tcp bug). Cheers, Tridge
- I also am getting hang/timeout using rsync 2.4.6 --daemon Dave Dykstra
- Re: I also am getting hang/timeout using rsync 2.4.6 ... Andrew Tridgell
- Re: I also am getting hang/timeout using rsync 2.... Dave Dykstra
- Re: I also am getting hang/timeout using rsyn... Eric Whiting
- Re: I also am getting hang/timeout using ... Eric Whiting
- Re: I also am getting hang/timeout using ... Andrew Tridgell
- Re: I also am getting hang/timeout using rsyn... Andrew Tridgell
- Re: I also am getting hang/timeout using ... Dave Dykstra
- Re: I also am getting hang/timeout using rsyn... Dave Dykstra
- Re: I also am getting hang/timeout using ... Dave Dykstra
- Re: I also am getting hang/timeout u... Andrew Tridgell
