In message , Richard Kettlewell
 writes
>You need to trace the ssh processes, on both hosts, not (just)
>rsync. Locally you could use ‘strace -tt -f’ to follow trace
>subprocesses as
>well. Remotely the easiest way is probably to attach the trace after
>things have started, with ‘strace -f -tt -p PID’.
>
>Attaching after things start means we don’t quite get the complete
>picture but since we’re looking for hints as to why things stop (or not)
>that may not matter.
>
>(-tt asks for timestamps, which makes it easier to match up events
>across the two hosts, assuming they both have correctly set clocks.)
>

Thanks, I'll have a got at that next time.

Adrian
--
To Reply :
replace "bulleid" with "adrian" - all mail to bulleid is rejected
Sorry for the rigmarole, If I want spam, I'll go to the shops
Every time someone says "I don't believe in trolls", another one dies.

--- SoupGate-Win32 v1.05