On Sat, Oct 21, 2000 at 05:04:56AM -0700, Harry Putnam wrote:
...
> > - versions of OS at both ends
>
> Redhat linux 6.2 FreeBSD-4.0
>
> > - versions of ssh at both ends
>
> ssh-1.2.27-5i SSH Version OpenSSH-2.1, protocol versions 1.5/2.0.
> Compiled with SSL (0x00904100).
>
> > - versions of rsync at both ends (2.4.6 from your mail)
> Linux box:
> rsync version 2.4.1 protocol version 24
>
> FreeBSD box:
> rsync version 2.4.3 protocol version 24
rsync 2.4.1 had known problems with hanging ssh. Are you initiating from
the Linux side? I think it only affects the initiating side. Please
upgrade to 2.4.6. I believe 2.4.3 was similar to 2.4.6 with respect to ssh
but it broke rsh connections. The difference between rsync 2.4.1 and 2.4.3
was that 2.4.3 set O_NONBLOCK on stdin & stdout to ssh.
And has that ssh been compiled without USE_PIPES?
> > - netstat output at both ends when frozen
>
> Linux Box:
> [209rt]~ # netstat -t
> Active Internet connections (w/o servers)
> Proto Recv-Q Send-Q Local Address Foreign Address State
...
> tcp 0 45288 reader.local.lan:1020 satellite.local.lan:ssh ESTABLISHED
...
> FreeBSD box:
> bsd # netstat -t
> Active Internet connections
> Proto Recv-Q Send-Q Local Address Foreign Address (state)
...
> tcp4 0 0 satellite.ssh reader.1020 ESTABLISHED
...
I don't know what netstat used to look like with the hangs rsync 2.4.1 had
over ssh, but the above numbers indicate that either the Linux or FreeBSD
operating systems are at fault for not transmitting the send Q from Linux
to FreeBSD.
- Dave Dykstra
