search for: vp222

On Wed, 2016-10-12 at 08:36 +0200, Paul Slootman wrote: > As always it's best to first upgrade to the current version (3.1.3) > if at all possible, as there's always the chance that the cause of > your problems has already been fixed. Good call, but I believe I may have ruled this out. I didn't upgrade to 3.1.3, but both sides are running 3.1.1 protocol version 31 now. Same

...ssh but if you are you can also debug the ssh layer. You can even do it at both ends.... On the server run a debugging sshd on an alternate port with: /usr/sbin/sshd -dDp222 (note that this will only accept 1 connection, debug to the terminal, then exit) then on the client use rsync -e "ssh -vp222" to go verbose and use the debugging port. On 10/13/2016 08:05 PM, Kip Warner wrote: > On Thu, 2016-10-13 at 16:58 -0700, Wayne Davison wrote: >> No, that's totally expected. While select() is waiting for I/O to >> arrive, it returns to rsync every 60 seconds to allow it to...

...o debug the ssh layer.  You can even do > it at both ends.... > > On the server run a debugging sshd on an alternate port with: > /usr/sbin/sshd -dDp222 > (note that this will only accept 1 connection, debug to the terminal, > then exit) then on the client use rsync -e "ssh -vp222" to go verbose > and use the debugging port. Hey Kevin, I managed to get a chance to try your suggestion. I noticed something very interesting. On the server side, there's actually two processes of rsync that appear to be spawned by the client's connection.  Running the ssh daemo...